characterList_ODD

Table of contents

TEI Complete

This TEI customization describes a schema that includes all of the TEI P5 modules. This is a very useful starting place for manually creating your own customizations — it is much easier to delete the modules you do not want than to add the modules you do. Furthermore this customization often proves helpful for testing TEI software.

However, this particular TEI customization is not recommended for actual use for encoding documents. It produces schemas and reference documentation that will be much larger and include many more elements than almost anyone could conceivably ever need. Tempting though it may be simply to have absolutely everything, and ‘just ignore’ elements not required, experience has shown that their presence makes the documentation harder to read and use, and makes a schema that is far more lax than desired.

The n attribute of each <moduleRef> below reflects the chapter number of the TEI Guidelines in which the module being referenced is defined. Note that the modules are generally referred to in the order defined, with the exception that the module for Simple Analytic Mechanisms is referred to before the module for Dictionaries. This is because the class att.lexicographic.normalized (which is defined in analysis) needs to be specified before the class att.lexicographic (which is defined in dictionaries).

The first four modules are often called the ‘required’ modules. However, these modules are not themselves technically required to create a TEI conformant markup language (let alone a useful non-TEI conformant markup language). Rather, they each contain one or more elements which are required for TEI conformance.

1. Elements

1.1. <TEI>

<TEI> (TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple <TEI> elements may be combined within a <TEI> (or <teiCorpus>) element. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
versionspecifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Member of
Contained by
core: teiCorpus
textstructure: TEI
May contain
header: teiHeader
textstructure: TEI text
Note

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, for example: <TEI version="4.4.0" xml:lang="it" xmlns="http://www.tei-c.org/ns/1.0">.

Example
<TEI version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>The shortest TEI Document Imaginable</title>    </titleStmt>    <publicationStmt>     <p>First published as part of TEI P2, this is the P5          version using a namespace.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <text>   <body>    <p>This is about the shortest TEI document imaginable.</p>   </body>  </text> </TEI>
Example
<TEI version="2.9.1" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader>   <fileDesc>    <titleStmt>     <title>A TEI Document containing four page images </title>    </titleStmt>    <publicationStmt>     <p>Unpublished demonstration file.</p>    </publicationStmt>    <sourceDesc>     <p>No source: this is an original work.</p>    </sourceDesc>   </fileDesc>  </teiHeader>  <facsimile>   <graphic url="page1.png"/>   <graphic url="page2.png"/>   <graphic url="page3.png"/>   <graphic url="page4.png"/>  </facsimile> </TEI>
Schematron
<sch:ns prefix="tei"  uri="http://www.tei-c.org/ns/1.0"/> <sch:ns prefix="xs"  uri="http://www.w3.org/2001/XMLSchema"/>
Schematron
<sch:ns prefix="rng"  uri="http://relaxng.org/ns/structure/1.0"/> <sch:ns prefix="rna"  uri="http://relaxng.org/ns/compatibility/annotations/1.0"/>
Schematron
<sch:ns prefix="sch"  uri="http://purl.oclc.org/dsdl/schematron"/> <sch:ns prefix="sch1x"  uri="http://www.ascc.net/xml/schematron"/>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <alternate>
   <sequence>
    <classRef key="model.resource"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="TEI" minOccurs="0"
     maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="TEI" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element TEI
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute version { text }?,
   ( tei_teiHeader, ( ( tei_model.resource+, tei_TEI* ) | tei_TEI+ ) )
}

1.2. <abbr>

<abbr> (abbreviation) contains an abbreviation of any sort. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
type(type) allows the encoder to classify the abbreviation according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
suspension
(suspension) the abbreviation provides the first letter(s) of the word or phrase, omitting the remainder.
contraction
(contraction) the abbreviation omits some letter(s) in the middle.
brevigraph
the abbreviation comprises a special symbol or mark.
superscription
(superscription) the abbreviation includes writing above the line.
acronym
(acronym) the abbreviation comprises the initial letters of the words of a phrase.
title
(title) the abbreviation is for a title of address (Dr, Ms, Mr, …)
organization
(organization) the abbreviation is for the name of an organization.
geographic
(geographic) the abbreviation is for a geographic name.
Note

The type attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use. For a typology of Middle English abbreviations, see 6.2.

Member of
Contained by
May contain
Note

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
<choice>  <expan>North Atlantic Treaty Organization</expan>  <abbr cert="low">NorATO</abbr>  <abbr cert="high">NATO</abbr>  <abbr cert="highxml:lang="fr">OTAN</abbr> </choice>
Example
<choice>  <abbr>SPQR</abbr>  <expan>senatus populusque romanorum</expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element abbr
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.3. <abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
Note

This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a <div> within the <front>, as it should for a born-digital document.

Example
<profileDesc>  <abstract resp="#LB">   <p>Good database design involves the acquisition and deployment of      skills which have a wider relevance to the educational process. From      a set of more or less instinctive rules of thumb a formal discipline      or "methodology" of database design has evolved. Applying that      methodology can be of great benefit to a very wide range of academic      subjects: it requires fundamental skills of abstraction and      generalisation and it provides a simple mechanism whereby complex      ideas and information structures can be represented and manipulated,      even without the use of a computer. </p>  </abstract> </profileDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <elementRef key="listBibl"/>
 </alternate>
</content>
    
Schema Declaration
element abstract
{
   tei_att.global.attributes,
   ( tei_model.pLike | tei_model.listLike | tei_listBibl )+
}

1.4. <add>

<add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.

In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project.

Example
The story I am going to relate is true as to its main facts, and as to the consequences <add place="above">of these facts</add> from which this tale takes its title.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element add
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.placement.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.5. <addName>

<addName> (additional name) contains an additional name component, such as a nickname, epithet, or alias, or any other descriptive phrase used within a personal name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Frederick</forename>  <addName type="epithet">the Great</addName>  <roleName>Emperor of Prussia</roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addName
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.6. <addrLine>

<addrLine> (address line) contains one line of a postal address. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
core: address
May contain
Note

Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text.

Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL</addrLine>  <addrLine>60680 USA</addrLine> </address>
Example
<addrLine>  <ref target="tel:+1-201-555-0123">(201) 555 0123</ref> </addrLine>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element addrLine { tei_att.global.attributes, tei_macro.phraseSeq }

1.7. <address>

<address> (address) contains a postal address, for example of a publisher, an organization, or an individual. [3.6.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
May contain
Note

This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc.

ExampleUsing just the elements defined by the core module, an address could be represented as follows:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <name>Bologna</name>  <name>Italy</name> </address>
ExampleWhen a schema includes the names and dates module more specific elements such as country or settlement would be preferable over generic <name>:
<address>  <street>via Marsala 24</street>  <postCode>40126</postCode>  <settlement>Bologna</settlement>  <country>Italy</country> </address>
Example
<address>  <addrLine>Computing Center, MC 135</addrLine>  <addrLine>P.O. Box 6998</addrLine>  <addrLine>Chicago, IL 60680</addrLine>  <addrLine>USA</addrLine> </address>
Example
<address>  <country key="FR"/>  <settlement type="city">Lyon</settlement>  <postCode>69002</postCode>  <district type="arrondissement">IIème</district>  <district type="quartier">Perrache</district>  <street>   <num>30</num>, Cours de Verdun</street> </address>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.addrPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element address
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.global*, ( ( tei_model.addrPart, tei_model.global* )+ ) )
}

1.8. <affiliation>

<affiliation> (affiliation) contains an informal description of a person's present or past affiliation with some organization, for example an employer or sponsor. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
sponsor
recommend
discredit
pledged
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

If included, the name of an organization may be tagged using either the <name> element as above, or the more specific <orgName> element.

Example
<affiliation>Junior project officer for the US <name type="org">National Endowment for    the Humanities</name> </affiliation>
ExampleThis example indicates that the person was affiliated with the Australian Journalists Association at some point between the dates listed.
<affiliation notAfter="1960-01-01"  notBefore="1957-02-28">Paid up member of the <orgName>Australian Journalists Association</orgName> </affiliation>
ExampleThis example indicates that the person was affiliated with Mount Holyoke College throughout the entire span of the date range listed.
<affiliation from="1902-01-01"  to="1906-01-01">Was an assistant professor at Mount Holyoke College.</affiliation>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element affiliation
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.9. <age>

<age> (age) specifies the age of a person. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
western
sui
subjective
objective
inWorld
(in world) age of a fictional character at the time the story takes place, rather than at the time the story is told
chronological
biological
psychological
functional
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
valuesupplies a numeric code representing the age or age group
StatusOptional
Datatypeteidata.count
Note

This attribute may be used to complement a more detailed discussion of a person's age in the content of the element

Member of
Contained by
May contain
Note

As with other culturally-constructed traits such as sex, the way in which this concept is described in different cultural contexts may vary. The normalizing attributes are provided as a means of simplifying that variety to Western European norms and should not be used where that is inappropriate. The content of the element may be used to describe the intended concept in more detail, using plain text.

Example
<age value="2notAfter="1986">under 20 in the early eighties</age>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element age
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.dimensions.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute value { text }?,
   tei_macro.phraseSeq.limited
}

1.10. <altIdent>

<altIdent> (alternate identifier) supplies the recommended XML name for an element, class, attribute, etc. in some language. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Moduletagdocs
Attributes
Member of
Contained by
May contain
XSD NCName
Note

All documentation elements in ODD have a canonical name, supplied as the value for their ident attribute. The <altIdent> element is used to supply an alternative name for the corresponding XML object, perhaps in a different language.

Example
<altIdent xml:lang="fr">balisageDoc</altIdent>
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Schema Declaration
element altIdent
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   xsd:NCName
}

1.11. <alternate>

<alternate> indicates that the constructs referenced by its children form an alternation [23.5.1. Defining Content Models]
Moduletagdocs
Attributes
Member of
Contained by
May contain
Example
<content>  <alternate>   <elementRef key="name"/>   <elementRef key="persName"/>  </alternate> </content>
This example content model permits either a <name> or a <persName>.
Schematron
<sch:rule context="tei:alternate"> <sch:assert test="count(*) gt 1">The alternate element must have at least two child elements</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <elementRef key="valList"/>
  <classRef key="model.contentPart"/>
 </alternate>
</content>
    
Schema Declaration
element alternate
{
   tei_att.global.attributes,
   tei_att.repeatable.attributes,
   ( tei_valList | tei_model.contentPart )+
}

1.12. <analytic>

<analytic> (analytic level) contains bibliographic elements describing an item (e.g. an article or poem) published within a monograph or journal and not as an independent publication. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
May contain
Note

May contain titles and statements of responsibility (author, editor, or other), in any order.

The <analytic> element may only occur within a <biblStruct>, where its use is mandatory for the description of an analytic level bibliographic item.

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope>377–380</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="author"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="date"/>
  <elementRef key="textLang"/>
  <elementRef key="idno"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element analytic
{
   tei_att.global.attributes,
   (
      tei_author
    | tei_editor
    | tei_respStmt
    | tei_title
    | tei_model.ptrLike
    | tei_date
    | tei_textLang
    | tei_idno
    | tei_availability
   )*
}

1.13. <anyElement>

<anyElement> indicates the presence of any elements in a content model [23. Documentation Elements]
Moduletagdocs
Attributes
requiresupplies a list of namespaces to one of which the permitted elements must belong.
StatusOptional
Datatype1–∞ occurrences of teidata.namespace separated by whitespace
exceptsupplies a list of namespaces or prefixed element names which are not permitted.
StatusOptional
Datatype1–∞ occurrences of teidata.namespaceOrName separated by whitespace
Note

When RELAX NG DTD Compatibility Mode is turned on, validation requires that any elements which may take an xml:id be excluded from the content of anyName name classes. For normal TEI purposes, this includes anything in the TEI namespace and the <egXML> element. Default elements and namespaces to be excluded are set on the defaultExceptions attribute of the <schemaSpec>. except may be used when the exceptions need to be locally specified. Element prefixes must be declared using a namespace declaration on the parent or an ancestor element.

Member of
Contained by
May containEmpty element
Example
<content>  <anyElement except="http://www.tei-c.org/ns/1.0"/> </content>
This <content> element permits one occurrence of any element which does not belong to the TEI namespace.
Example
<content>  <anyElement minOccurs="1"   maxOccurs="unbounded"   require="http://www.w3.org/1998/Math/MathML http://www.tei-c.org/ns/Examples/1.0"/> </content>
This <content> element permits one or more elements which belong either to the MathML namespace or to the TEI examples namespace.
Example
<content>  <alternate minOccurs="1"   maxOccurs="unbounded">   <textNode/>   <anyElement require="http://www.tei-c.org/ns/Examples/1.0"/>  </alternate> </content>
This <content> element permits one or more children which are either text nodes or elements from the TEI examples namespace. It is the equivalent of the content model ANY in an XML DTD using the TEI All schema.
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element anyElement
{
   tei_att.global.attributes,
   tei_att.repeatable.attributes,
   attribute require { list { + } }?,
   attribute except { list { + } }?,
   empty
}

1.14. <appInfo>

<appInfo> (application information) records information about an application which has edited the TEI file. [2.3.11. The Application Information Element]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: application
Example
<appInfo>  <application version="1.24ident="Xaira">   <label>XAIRA Indexer</label>   <ptr target="#P1"/>  </application> </appInfo>
Content model
<content>
 <classRef key="model.applicationLike"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element appInfo { tei_att.global.attributes, tei_model.applicationLike+ }

1.15. <application>

<application> provides information about an application which has acted upon the document. [2.3.11. The Application Information Element]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
identsupplies an identifier for the application, independent of its version number or display name.
StatusRequired
Datatypeteidata.name
versionsupplies a version number for the application, independent of its identifier or display name.
StatusRequired
Datatypeteidata.versionNumber
Member of
Contained by
header: appInfo
May contain
tagdocs: listRef
Example
<appInfo>  <application version="1.5"   ident="ImageMarkupTool1notAfter="2006-06-01">   <label>Image Markup Tool</label>   <ptr target="#P1"/>   <ptr target="#P2"/>  </application> </appInfo>
This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.
Content model
<content>
 <sequence>
  <classRef key="model.labelLike"
   minOccurs="1" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.ptrLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element application
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   attribute ident { text },
   attribute version { text },
   ( tei_model.labelLike+, ( tei_model.ptrLike* | tei_model.pLike* ) )
}

1.16. <argument>

<argument> (argument) contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<argument>  <p>Monte Video — Maldonado — Excursion    to R Polanco — Lazo and Bolas — Partridges —    Absence of Trees — Deer — Capybara, or River Hog —    Tucutuco — Molothrus, cuckoo-like habits — Tyrant    Flycatcher — Mocking-bird — Carrion Hawks —    Tubes formed by Lightning — House struck</p> </argument>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.headLike"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.common"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element argument
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      ( tei_model.global | tei_model.headLike )*,
      ( ( tei_model.common, tei_model.global* )+ )
   )
}

1.17. <att>

<att> (attribute) contains the name of an attribute appearing within running text. [23. Documentation Elements]
Moduletagdocs
Attributes
scheme(scheme) supplies an identifier for the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(Text Encoding Initiative) this attribute is part of the TEI scheme.[Default]
DBK
(Docbook) this attribute is part of the Docbook scheme.
XX
(unknown) this attribute is part of an unknown scheme.
imaginary
(imaginary) the attribute is from a non-existent scheme, for illustrative purposes only
XHTML
(XHTML) the attribute is part of the XHTML language
XML
(XML) the attribute is part of the XML language
XI
(XI) the attribute is defined in the xInclude schema
Member of
Contained by
May contain
XSD Name
Note

As an alternative to using the scheme attribute a namespace prefix may be used. Where both scheme and a prefix are used, the prefix takes precedence.

Example
<p>The TEI defines several <soCalled>global</soCalled> attributes; their names include <att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>, and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p>
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element att
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}

1.18. <attDef>

<attDef> (attribute definition) contains the definition of a single attribute. [23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
usagespecifies the optionality of the attribute.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
req
(required)
rec
(recommended )
opt
(optional ) [Default]
Contained by
tagdocs: attList
May contain
Example
<attDef usage="recident="type">  <desc>specifies a name conventionally used for this level of subdivision, e.g.  <val>act</val>, <val>volume</val>, <val>book</val>, <val>section</val>, <val>canto</val>,    etc.</desc>  <datatype>   <dataRef key="teidata.word"/>  </datatype> </attDef>
Schematron
<sch:ns prefix="teix"  uri="http://www.tei-c.org/ns/Examples"/> <sch:rule context="tei:attDef"> <sch:assert test="ancestor::teix:egXML[ @valid eq 'feasible'] or @mode eq 'change' or @mode eq 'delete' or tei:datatype or tei:valList[ @type eq 'closed']"> Attribute: the definition of the @<sch:value-of select="@ident"/> attribute in the <sch:value-of select="ancestor::*[@ident][1]/@ident"/>  <sch:value-of select="' '"/>  <sch:value-of select="local-name(ancestor::*[@ident][1])"/> should have a closed valList or a datatype </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:attDef[@usage eq 'req']"> <sch:report test="tei:defaultVal">Since the @<sch:value-of select="@ident"/> attribute is required, it will always be specified. Thus the default value (of "<sch:value-of select="normalize-space(tei:defaultVal)"/>") will never be used. Either change the definition of the attribute so it is not required ("rec" or "opt"), or remove the defaultVal element.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:attDef[ tei:defaultVal and tei:valList[ @type eq 'closed'] and tei:datatype[ @maxOccurs > 1 or @minOccurs > 1 or @maxOccurs eq 'unbounded'] ]"> <sch:assert test="tokenize(normalize-space(tei:defaultVal),' ') = tei:valList/tei:valItem/@ident">In the <sch:value-of select="local-name(ancestor::*[@ident][1])"/> defining <sch:value-of select="ancestor::*[@ident][1]/@ident"/> the default value of the @<sch:value-of select="@ident"/> attribute is not among the closed list of possible values</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:attDef[ tei:defaultVal and tei:valList[ @type eq 'closed'] and tei:datatype[ not(@maxOccurs) or ( if ( @maxOccurs castable as xs:integer ) then ( @maxOccurs cast as xs:integer eq 1 ) else false() ) ] ]"> <sch:assert test="string(tei:defaultVal) = tei:valList/tei:valItem/@ident">In the <sch:value-of select="local-name(ancestor::*[@ident][1])"/> defining <sch:value-of select="ancestor::*[@ident][1]/@ident"/> the default value of the @<sch:value-of select="@ident"/> attribute is not among the closed list of possible values</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="datatype" minOccurs="0"/>
  <elementRef key="constraintSpec"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="defaultVal"
   minOccurs="0"/>
  <alternate minOccurs="0">
   <elementRef key="valList"/>
   <elementRef key="valDesc" minOccurs="1"
    maxOccurs="unbounded"/>
  </alternate>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element attDef
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.namespaceable.attributes,
   attribute usage { "req" | "rec" | "opt" }?,
   (
      ( tei_model.identSynonyms | tei_model.descLike )*,
      tei_datatype?,
      tei_constraintSpec*,
      tei_defaultVal?,
      ( tei_valList | tei_valDesc+ )?,
      tei_exemplum*,
      tei_remarks*
   )
}

1.19. <attList>

<attList> (attribute list) contains documentation for all the attributes associated with this element, as a series of <attDef> elements. [23.5. Element Specifications 23.6. Class Specifications]
Moduletagdocs
Attributes
org(organization) specifies whether only one (choice) or all (group) of the attributes in the list are available
StatusOptional
Datatypeteidata.enumerated
Legal values are:
group
grouped[Default]
choice
alternated
Contained by
May contain
Example
<attList>  <attDef ident="typeusage="opt">   <desc>type of schema</desc>   <datatype>    <dataRef key="teidata.enumerated"/>   </datatype>  </attDef> </attList>
Example
<attList org="choice">  <attDef ident="active">   <desc versionDate="2005-07-24"    xml:lang="en">identifies the <soCalled>active</soCalled> participants in a non-mutual relationship, or all the participants in a mutual      one.</desc>   <datatype maxOccurs="unbounded">    <dataRef key="teidata.pointer"/>   </datatype>  </attDef>  <attDef ident="mutualusage="opt">   <desc versionDate="2005-07-24"    xml:lang="en">supplies a list of participants amongst all of whom the relationship holds equally.</desc>   <datatype maxOccurs="unbounded">    <dataRef key="teidata.pointer"/>   </datatype>  </attDef> </attList>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <elementRef key="attRef"/>
  <elementRef key="attDef"/>
  <elementRef key="attList"/>
 </alternate>
</content>
    
Schema Declaration
element attList
{
   tei_att.global.attributes,
   attribute org { "group" | "choice" }?,
   ( tei_attRef | tei_attDef | tei_attList )+
}

1.20. <attRef>

<attRef> (attribute pointer) points to the definition of an attribute or group of attributes. [23.2. Modules and Schemas]
Moduletagdocs
Attributes
classthe name of the attribute class
StatusOptional
Datatypeteidata.name
namethe name of the attribute
StatusOptional
Datatypeteidata.name
Contained by
tagdocs: attList
May containEmpty element
Example
<attRef class="att.globalname="xml:id"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element attRef
{
   tei_att.global.attributes,
   attribute class { text }?,
   attribute name { text }?,
   empty
}

1.21. <author>

<author> (author) in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

Example
<author>British Broadcasting Corporation</author> <author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author> <author>Anonymous</author> <author>Bill and Melinda Gates Foundation</author> <author>  <persName>Beaumont, Francis</persName> and <persName>John Fletcher</persName> </author> <author>  <orgName key="BBC">British Broadcasting    Corporation</orgName>: Radio 3 Network </author>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element author
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.22. <authority>

<authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
core: monogr
May contain
Example
<authority>John Smith</authority>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element authority
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq.limited
}

1.23. <availability>

<availability> (availability) supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
status(status) supplies a code identifying the current availability of the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
free
(free) the text is freely available.
unknown
(unknown) the status of the text is unknown.
restricted
(restricted) the text is not freely available.
Member of
Contained by
May contain
core: p
header: licence
Note

A consistent format should be adopted

Example
<availability status="restricted">  <p>Available for academic research purposes only.</p> </availability> <availability status="free">  <p>In the public domain</p> </availability> <availability status="restricted">  <p>Available under licence from the publishers.</p> </availability>
Example
<availability>  <licence target="http://opensource.org/licenses/MIT">   <p>The MIT License      applies to this document.</p>   <p>Copyright (C) 2011 by The University of Victoria</p>   <p>Permission is hereby granted, free of charge, to any person obtaining a copy      of this software and associated documentation files (the "Software"), to deal      in the Software without restriction, including without limitation the rights      to use, copy, modify, merge, publish, distribute, sublicense, and/or sell      copies of the Software, and to permit persons to whom the Software is      furnished to do so, subject to the following conditions:</p>   <p>The above copyright notice and this permission notice shall be included in      all copies or substantial portions of the Software.</p>   <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR      IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,      FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE      AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER      LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,      OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN      THE SOFTWARE.</p>  </licence> </availability>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.availabilityPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element availability
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute status { "free" | "unknown" | "restricted" }?,
   ( tei_model.availabilityPart | tei_model.pLike )+
}

1.24. <back>

<back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Note

Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical.

Example
<back>  <div type="appendix">   <head>The Golden Dream or, the Ingenuous Confession</head>   <p>TO shew the Depravity of human Nature, and how apt the Mind is to be misled by Trinkets      and false Appearances, Mrs. Two-Shoes does acknowledge, that after she became rich, she      had like to have been, too fond of Money <!-- .... -->   </p>  </div> <!-- ... -->  <div type="epistle">   <head>A letter from the Printer, which he desires may be inserted</head>   <salute>Sir.</salute>   <p>I have done with your Copy, so you may return it to the Vatican, if you please;    <!-- ... -->   </p>  </div>  <div type="advert">   <head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr      Newbery's at the Bible and Sun in St Paul's Church-yard.</head>   <list>    <item n="1">The Christmas Box, Price 1d.</item>    <item n="2">The History of Giles Gingerbread, 1d.</item> <!-- ... -->    <item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,        10 Vol, Pr. bound 1l.</item>   </list>  </div>  <div type="advert">   <head>By the KING's Royal Patent, Are sold by J. NEWBERY, at the Bible and Sun in St.      Paul's Church-Yard.</head>   <list>    <item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &amp;c. 2s.        6d</item>    <item n="2">Dr. Hooper's Female Pills, 1s.</item> <!-- ... -->   </list>  </div> </back>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.pLike"/>
   <classRef key="model.listLike"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate minOccurs="0">
   <sequence>
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.div1Like"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
   <sequence>
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.frontPart"/>
     <classRef key="model.divLike"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0">
   <classRef key="model.divBottomPart"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottomPart"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element back
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike.front
       | tei_model.pLike
       | tei_model.listLike
       | tei_model.global
      )*,
      (
         (
            tei_model.div1Like,
            ( tei_model.frontPart | tei_model.div1Like | tei_model.global )*
         )
       | (
            tei_model.divLike,
            ( tei_model.frontPart | tei_model.divLike | tei_model.global )*
         )
      )?,
      (
         (
            tei_model.divBottomPart,
            ( tei_model.divBottomPart | tei_model.global )*
         )?
      )
   )
}

1.25. <bibl>

<bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Contains phrase-level elements, together with any combination of elements from the model.biblPart class

Example
<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990)</bibl>
Example
<bibl>  <title level="a">The Interesting story of the Children in the Wood</title>. In <author>Victor E Neuberg</author>, <title>The Penny Histories</title>. <publisher>OUP</publisher>  <date>1968</date>. </bibl>
Example
<bibl type="articlesubtype="book_chapter"  xml:id="carlin_2003">  <author>   <name>    <surname>Carlin</surname>      (<forename>Claire</forename>)</name>  </author>, <title level="a">The Staging of Impotence : France’s last    congrès</title> dans <bibl type="monogr">   <title level="m">Theatrum mundi : studies in honor of Ronald W.      Tobin</title>, éd.  <editor>    <name>     <forename>Claire</forename>     <surname>Carlin</surname>    </name>   </editor> et  <editor>    <name>     <forename>Kathleen</forename>     <surname>Wine</surname>    </name>   </editor>,  <pubPlace>Charlottesville, Va.</pubPlace>,  <publisher>Rookwood Press</publisher>,  <date when="2003">2003</date>.  </bibl> </bibl>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.highlighted"/>
  <classRef key="model.pPart.data"/>
  <classRef key="model.pPart.edit"/>
  <classRef key="model.segLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.biblPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element bibl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.highlighted
    | tei_model.pPart.data
    | tei_model.pPart.edit
    | tei_model.segLike
    | tei_model.ptrLike
    | tei_model.biblPart
    | tei_model.global
   )*
}

1.26. <biblFull>

<biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<biblFull>  <titleStmt>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>  </titleStmt>  <editionStmt>   <edition>UK edition</edition>  </editionStmt>  <extent>1231 pp</extent>  <publicationStmt>   <publisher>Yale University Press</publisher>   <pubPlace>New Haven and London</pubPlace>   <date>1990</date>  </publicationStmt>  <sourceDesc>   <p>No source: this is an original work</p>  </sourceDesc> </biblFull>
Content model
<content>
 <alternate>
  <sequence>
   <sequence>
    <elementRef key="titleStmt"/>
    <elementRef key="editionStmt"
     minOccurs="0"/>
    <elementRef key="extent" minOccurs="0"/>
    <elementRef key="publicationStmt"/>
    <elementRef key="seriesStmt"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="notesStmt"
     minOccurs="0"/>
   </sequence>
   <elementRef key="sourceDesc"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence>
   <elementRef key="fileDesc"/>
   <elementRef key="profileDesc"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element biblFull
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   tei_att.cmc.attributes,
   (
      (
         (
            tei_titleStmt,
            tei_editionStmt?,
            tei_extent?,
            tei_publicationStmt,
            tei_seriesStmt*,
            tei_notesStmt?
         ),
         tei_sourceDesc*
      )
    | ( tei_fileDesc, tei_profileDesc )
   )
}

1.27. <biblScope>

<biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <biblScope from="3">p. 3ff</biblScope>.

It is now considered good practice to supply this element as a sibling (rather than a child) of <imprint>, since it supplies information which does not constitute part of the imprint.

Example
<biblScope>pp 12–34</biblScope> <biblScope unit="pagefrom="12to="34"/> <biblScope unit="volume">II</biblScope> <biblScope unit="page">12</biblScope>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element biblScope
{
   tei_att.global.attributes,
   tei_att.citing.attributes,
   tei_macro.phraseSeq
}

1.28. <biblStruct>

<biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<biblStruct>  <monogr>   <author>Blain, Virginia</author>   <author>Clements, Patricia</author>   <author>Grundy, Isobel</author>   <title>The Feminist Companion to Literature in English: women writers from the middle ages      to the present</title>   <edition>first edition</edition>   <imprint>    <publisher>Yale University Press</publisher>    <pubPlace>New Haven and London</pubPlace>    <date>1990</date>   </imprint>  </monogr> </biblStruct>
Example
<biblStruct type="newspaper">  <analytic>   <author>    <forename>David</forename>    <surname>Barstow</surname>   </author>   <author>    <forename>Susanne</forename>    <surname>Craig</surname>   </author>   <author>    <forename>Russ</forename>    <surname>Buettner</surname>   </author>   <title type="main">Trump Took Part in Suspect Schemes to Evade Tax Bills</title>   <title type="sub">Behind the Myth of a Self-Made Billionaire, a Vast Inheritance From His Father</title>  </analytic>  <monogr>   <title level="j">The New York Times</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>A. G. Sulzberger</publisher>    <date when="2018-10-03">Wednesday, October 3, 2018</date>   </imprint>   <biblScope unit="volume">CLXVIII</biblScope>   <biblScope unit="issue">58,104</biblScope>   <biblScope unit="page">1</biblScope>  </monogr> </biblStruct>
Content model
<content>
 <sequence>
  <elementRef key="analytic" minOccurs="0"
   maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="monogr"/>
   <elementRef key="series" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.ptrLike"/>
   <elementRef key="relatedItem"/>
   <elementRef key="citedRange"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element biblStruct
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.docStatus.attributes,
   tei_att.cmc.attributes,
   (
      tei_analytic*,
      ( ( tei_monogr, tei_series* )+ ),
      (
         tei_model.noteLike
       | tei_model.ptrLike
       | tei_relatedItem
       | tei_citedRange
      )*
   )
}

1.29. <binaryObject>

<binaryObject> provides encoded binary data representing an inline graphic, audio, video or other object. [3.10. Graphics and Other Non-textual Components]
Modulecore
Attributes
encodingThe encoding used to encode the binary data. If not specified, this is assumed to be Base64.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May containCharacter data only
Example
<binaryObject mimeType="image/gif"> R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAwAAAC8IyPqcvt3wCcDkiLc7C0qwy GHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFzByTB10QgxOR0TqBQejhRNzOfkVJ +5YiUqrXF5Y5lKh/DeuNcP5yLWGsEbtLiOSpa/TPg7JpJHxyendzWTBfX0cxOnK PjgBzi4diinWGdkF8kjdfnycQZXZeYGejmJlZeGl9i2icVqaNVailT6F5iJ90m6 mvuTS4OK05M0vDk0Q4XUtwvKOzrcd3iq9uisF81M1OIcR7lEewwcLp7tuNNkM3u Nna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH hhx4dbgYKAAA7</binaryObject>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element binaryObject
{
   tei_att.global.attributes,
   tei_att.media.attributes,
   tei_att.timed.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute encoding { list { + } }?,
   text
}

1.30. <birth>

<birth> (birth) contains information about a person's birth, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
caesarean
(caesarean section)
vaginal
(vaginal delivery)
exNihilo
(ex nihilo)
incorporated
founded
established
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<birth>Before 1920, Midlands region.</birth>
Example
<birth when="1960-12-10">In a small cottage near <name type="place">Aix-la-Chapelle</name>, early in the morning of <date>10 Dec 1960</date> </birth>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element birth
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.31. <bloc>

<bloc> (bloc) contains the name of a geo-political unit consisting of two or more nation states or countries. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<bloc type="union">the European Union</bloc> <bloc type="continent">Africa</bloc>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element bloc
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.32. <body>

<body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Example
<body>  <l>Nu scylun hergan hefaenricaes uard</l>  <l>metudæs maecti end his modgidanc</l>  <l>uerc uuldurfadur sue he uundra gihuaes</l>  <l>eci dryctin or astelidæ</l>  <l>he aerist scop aelda barnum</l>  <l>heben til hrofe haleg scepen.</l>  <l>tha middungeard moncynnæs uard</l>  <l>eci dryctin æfter tiadæ</l>  <l>firum foldu frea allmectig</l>  <trailer>primo cantauit Cædmon istud carmen.</trailer> </body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <classRef key="model.divTop"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divTop"/>
   </alternate>
  </sequence>
  <sequence minOccurs="0">
   <classRef key="model.divGenLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.global"/>
    <classRef key="model.divGenLike"/>
   </alternate>
  </sequence>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.divLike"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.div1Like"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.global"/>
     <classRef key="model.divGenLike"/>
    </alternate>
   </sequence>
   <sequence>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate minOccurs="1" maxOccurs="1">
      <elementRef key="schemaSpec"/>
      <classRef key="model.common"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <alternate minOccurs="0">
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <alternate minOccurs="0"
       maxOccurs="unbounded">
       <classRef key="model.global"/>
       <classRef key="model.divGenLike"/>
      </alternate>
     </sequence>
    </alternate>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element body
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      tei_model.global*,
      ( ( tei_model.divTop, ( tei_model.global | tei_model.divTop )* )? ),
      (
         ( tei_model.divGenLike, ( tei_model.global | tei_model.divGenLike )* )?
      ),
      (
         (
            ( tei_model.divLike, ( tei_model.global | tei_model.divGenLike )* )+
         )
       | (
            (
               tei_model.div1Like,
               ( tei_model.global | tei_model.divGenLike )*
            )+
         )
       | (
            ( ( ( tei_schemaSpec | tei_model.common ), tei_model.global* )+ ),
            (
               (
                  (
                     tei_model.divLike,
                     ( tei_model.global | tei_model.divGenLike )*
                  )+
               )
             | (
                  (
                     tei_model.div1Like,
                     ( tei_model.global | tei_model.divGenLike )*
                  )+
               )
            )?
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

1.33. <byline>

<byline> (byline) contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docAuthor> element.

Example
<byline>Written by a CITIZEN who continued all the while in London. Never made publick before.</byline>
Example
<byline>Written from her own MEMORANDUMS</byline>
Example
<byline>By George Jones, Political Editor, in Washington</byline>
Example
<byline>BY <docAuthor>THOMAS PHILIPOTT,</docAuthor> Master of Arts, (Somtimes) Of Clare-Hall in Cambridge.</byline>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="docAuthor"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element byline
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_docAuthor
    | tei_model.global
   )*
}

1.34. <cRefPattern>

<cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
Attributes
Contained by
header: refsDecl
May contain
core: p
Note

The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"  replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element cRefPattern
{
   tei_att.global.attributes,
   tei_att.patternReplacement.attributes,
   tei_model.pLike*
}

1.35. <calendar>

<calendar> (calendar) describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description]
Moduleheader
Attributes
Contained by
header: calendarDesc
May contain
core: p
Example
<calendarDesc>  <calendar xml:id="julianEngland">   <p>Julian Calendar (including proleptic)</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendar
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_model.pLike+
}

1.36. <calendarDesc>

<calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
header: calendar
Note

In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country

Example
<calendarDesc>  <calendar xml:id="cal_AD">   <p>Anno Domini (Christian Era)</p>  </calendar>  <calendar xml:id="cal_AH">   <p>Anno Hegirae (Muhammedan Era)</p>  </calendar>  <calendar xml:id="cal_AME">   <p>Mauludi Era (solar years since Mohammed's birth)</p>  </calendar>  <calendar xml:id="cal_AM">   <p>Anno Mundi (Jewish Calendar)</p>  </calendar>  <calendar xml:id="cal_AP">   <p>Anno Persici</p>  </calendar>  <calendar xml:id="cal_AS">   <p>Aji Saka Era (Java)</p>  </calendar>  <calendar xml:id="cal_BE">   <p>Buddhist Era</p>  </calendar>  <calendar xml:id="cal_CB">   <p>Cooch Behar Era</p>  </calendar>  <calendar xml:id="cal_CE">   <p>Common Era</p>  </calendar>  <calendar xml:id="cal_CL">   <p>Chinese Lunar Era</p>  </calendar>  <calendar xml:id="cal_CS">   <p>Chula Sakarat Era</p>  </calendar>  <calendar xml:id="cal_EE">   <p>Ethiopian Era</p>  </calendar>  <calendar xml:id="cal_FE">   <p>Fasli Era</p>  </calendar>  <calendar xml:id="cal_ISO">   <p>ISO 8601 calendar</p>  </calendar>  <calendar xml:id="cal_JE">   <p>Japanese Calendar</p>  </calendar>  <calendar xml:id="cal_KE">   <p>Khalsa Era (Sikh calendar)</p>  </calendar>  <calendar xml:id="cal_KY">   <p>Kali Yuga</p>  </calendar>  <calendar xml:id="cal_ME">   <p>Malabar Era</p>  </calendar>  <calendar xml:id="cal_MS">   <p>Monarchic Solar Era</p>  </calendar>  <calendar xml:id="cal_NS">   <p>Nepal Samwat Era</p>  </calendar>  <calendar xml:id="cal_OS">   <p>Old Style (Julian Calendar)</p>  </calendar>  <calendar xml:id="cal_RS">   <p>Rattanakosin (Bangkok) Era</p>  </calendar>  <calendar xml:id="cal_SE">   <p>Saka Era</p>  </calendar>  <calendar xml:id="cal_SH">   <p>Mohammedan Solar Era (Iran)</p>  </calendar>  <calendar xml:id="cal_SS">   <p>Saka Samvat</p>  </calendar>  <calendar xml:id="cal_TE">   <p>Tripurabda Era</p>  </calendar>  <calendar xml:id="cal_VE">   <p>Vikrama Era</p>  </calendar>  <calendar xml:id="cal_VS">   <p>Vikrama Samvat Era</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Gregorian">   <p>Gregorian calendar</p>  </calendar>  <calendar xml:id="cal_Julian">   <p>Julian calendar</p>  </calendar>  <calendar xml:id="cal_Islamic">   <p>Islamic or Muslim (hijri) lunar calendar</p>  </calendar>  <calendar xml:id="cal_Hebrew">   <p>Hebrew or Jewish lunisolar calendar</p>  </calendar>  <calendar xml:id="cal_Revolutionary">   <p>French Revolutionary calendar</p>  </calendar>  <calendar xml:id="cal_Iranian">   <p>Iranian or Persian (Jalaali) solar calendar</p>  </calendar>  <calendar xml:id="cal_Coptic">   <p>Coptic or Alexandrian calendar</p>  </calendar>  <calendar xml:id="cal_Chinese">   <p>Chinese lunisolar calendar</p>  </calendar> </calendarDesc>
Example
<calendarDesc>  <calendar xml:id="cal_Egyptian"   target="http://en.wikipedia.org/wiki/Egyptian_calendar">   <p>Egyptian calendar (as defined by Wikipedia)</p>  </calendar> </calendarDesc>
Content model
<content>
 <elementRef key="calendar" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element calendarDesc { tei_att.global.attributes, tei_calendar+ }

1.37. <catDesc>

<catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal <textDesc>. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
header: category
May contain
Example
<catDesc>Prose reportage</catDesc>
Example
<catDesc>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc> </catDesc>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.catDescPart"/>
 </alternate>
</content>
    
Schema Declaration
element catDesc
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   ( text | tei_model.limitedPhrase | tei_model.catDescPart )*
}

1.38. <catRef>

<catRef> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification scheme within which the set of categories concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May containEmpty element
Note

The scheme attribute needs to be supplied only if more than one taxonomy has been declared.

Example
<catRef scheme="#myTopics"  target="#news #prov #sales2"/> <!-- elsewhere --> <taxonomy xml:id="myTopics">  <category xml:id="news">   <catDesc>Newspapers</catDesc>  </category>  <category xml:id="prov">   <catDesc>Provincial</catDesc>  </category>  <category xml:id="sales2">   <catDesc>Low to average annual sales</catDesc>  </category> </taxonomy>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element catRef
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   attribute scheme { text }?,
   empty
}

1.39. <category>

<category> (category) contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
core: desc gloss
tagdocs: equiv
Example
<category xml:id="b1">  <catDesc>Prose reportage</catDesc> </category>
Example
<category xml:id="b2">  <catDesc>Prose </catDesc>  <category xml:id="b11">   <catDesc>journalism</catDesc>  </category>  <category xml:id="b12">   <catDesc>fiction</catDesc>  </category> </category>
Example
<category xml:id="LIT">  <catDesc xml:lang="pl">literatura piękna</catDesc>  <catDesc xml:lang="en">fiction</catDesc>  <category xml:id="LPROSE">   <catDesc xml:lang="pl">proza</catDesc>   <catDesc xml:lang="en">prose</catDesc>  </category>  <category xml:id="LPOETRY">   <catDesc xml:lang="pl">poezja</catDesc>   <catDesc xml:lang="en">poetry</catDesc>  </category>  <category xml:id="LDRAMA">   <catDesc xml:lang="pl">dramat</catDesc>   <catDesc xml:lang="en">drama</catDesc>  </category> </category>
Content model
<content>
 <sequence>
  <alternate>
   <elementRef key="catDesc" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.descLike"/>
    <elementRef key="equiv"/>
    <elementRef key="gloss"/>
   </alternate>
  </alternate>
  <elementRef key="category" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element category
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   (
      ( tei_catDesc+ | ( tei_model.descLike | tei_equiv | tei_gloss )* ),
      tei_category*
   )
}

1.40. <cb>

<cb> (column beginning) marks the beginning of a new column of a text on a multi-column page. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb> element is placed at the head of the column to which it refers.

ExampleMarkup of an early English dictionary printed in two columns:
<pb/> <cb n="1"/> <entryFree>  <form>Well</form>, <sense>a Pit to hold Spring-Water</sense>: <sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner    sinks into the Ground, to find out and disappoint the Enemies Mines,    or to prepare one</sense>. </entryFree> <entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or <sense>lie groveling</sense>.</entryFree> <!-- remainder of column --> <cb n="2"/> <entryFree>  <form>Wey</form>, <sense>the greatest Measure for dry Things,    containing five Chaldron</sense>. </entryFree> <entryFree>  <form>Whale</form>, <sense>the greatest of    Sea-Fishes</sense>. </entryFree>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element cb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   empty
}

1.41. <change>

<change> (change) documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
target(target) points to one or more elements that belong to this change.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
Note

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

Example
<titleStmt>  <title> ... </title>  <editor xml:id="LDB">Lou Burnard</editor>  <respStmt xml:id="BZ">   <resp>copy editing</resp>   <name>Brett Zamir</name>  </respStmt> </titleStmt> <!-- ... --> <revisionDesc status="published">  <change who="#BZwhen="2008-02-02"   status="public">Finished chapter 23</change>  <change who="#BZwhen="2008-01-02"   status="draft">Finished chapter 2</change>  <change n="P2.2when="1991-12-21"   who="#LDB">Added examples to section 3</change>  <change when="1991-11-11who="#MSM">Deleted chapter 10</change> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange>    <change xml:id="DRAFT1">First draft in pencil</change>    <change xml:id="DRAFT2"     notBefore="1880-12-09">First revision, mostly        using green ink</change>    <change xml:id="DRAFT3"     notBefore="1881-02-13">Final corrections as        supplied to printer.</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element change
{
   tei_att.ascribed.attributes,
   tei_att.datable.attributes,
   tei_att.docStatus.attributes,
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute target { list { + } }?,
   tei_macro.specialPara
}

1.42. <choice>

<choice> (choice) groups a number of alternative encodings for the same point in a text. [3.5. Simple Editorial Changes]
Modulecore
Attributes
Member of
Contained by
May contain
Note

Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.

Note also that <choice> elements may self-nest.

Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 13.1. The Apparatus Entry, Readings, and Witnesses should be preferred.

ExampleAn American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows.
<p>Lastly, That, upon his solemn oath to observe all the above articles, the said man-mountain shall have a daily allowance of meat and drink sufficient for the support of <choice>   <sic>1724</sic>   <corr>1728</corr>  </choice> of our subjects, with free access to our royal person, and other marks of our <choice>   <orig>favour</orig>   <reg>favor</reg>  </choice>.</p>
Content model
<content>
 <alternate minOccurs="2"
  maxOccurs="unbounded">
  <classRef key="model.choicePart"/>
  <elementRef key="choice"/>
 </alternate>
</content>
    
Schema Declaration
element choice
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice ),
   ( tei_model.choicePart | tei_choice )*
}

1.43. <cit>

<cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 10.3.5.1. Examples]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<cit>  <quote>and the breath of the whale is frequently attended with such an insupportable smell,    as to bring on disorder of the brain.</quote>  <bibl>Ulloa's South America</bibl> </cit>
Example
<entry>  <form>   <orth>horrifier</orth>  </form>  <cit type="translationxml:lang="en">   <quote>to horrify</quote>  </cit>  <cit type="example">   <quote>elle était horrifiée par la dépense</quote>   <cit type="translationxml:lang="en">    <quote>she was horrified at the expense.</quote>   </cit>  </cit> </entry>
Example
<cit type="example">  <quote xml:lang="mix">Ka'an yu tsa'a Pedro.</quote>  <media url="soundfiles-gen:S_speak_1s_on_behalf_of_Pedro_01_02_03_TS.wav"   mimeType="audio/wav"/>  <cit type="translation">   <quote xml:lang="en">I'm speaking on behalf of Pedro.</quote>  </cit>  <cit type="translation">   <quote xml:lang="es">Estoy hablando de parte de Pedro.</quote>  </cit> </cit>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.biblLike"/>
  <classRef key="model.egLike"/>
  <classRef key="model.entryPart"/>
  <classRef key="model.global"/>
  <classRef key="model.graphicLike"/>
  <classRef key="model.ptrLike"/>
  <classRef key="model.attributable"/>
  <elementRef key="pc"/>
  <elementRef key="q"/>
 </alternate>
</content>
    
Schema Declaration
element cit
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.biblLike
    | tei_model.egLike
    | tei_model.entryPart
    | tei_model.global
    | tei_model.graphicLike
    | tei_model.ptrLike
    | tei_model.attributable
    | pc
    | tei_q
   )+
}

1.44. <citeData>

<citeData> (citation data) specifies how information may be extracted from citation structures. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader
Attributes
property(property) A URI indicating a property definition.
StatusRequired
Datatypeteidata.pointer
Contained by
May containEmpty element
Example
<citeStructure unit="book"  match="//body/divuse="@n">  <citeData property="http://purl.org/dc/terms/title"   use="head"/> </citeStructure>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element citeData
{
   tei_att.global.attributes,
   tei_att.citeStructurePart.attributes,
   attribute property { text },
   empty
}

1.45. <citeStructure>

<citeStructure> (citation structure) declares a structure and method for citing the current document. [3.11.4. Declaring Reference Systems 17.2.5.4. Citation Structures]
Moduleheader
Attributes
delim(delimiter) supplies a delimiting string preceding the structural component.
StatusOptional
Datatypestring
Note

delim must contain at least one character.

match(match) supplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]] which identifies a set of nodes which are citable structural components. The expression may be absolute (beginning with /) or relative. match on a <citeStructure> without a <citeStructure> parent must be an absolute XPath. If it is relative, its context is set by the match of the parent <citeStructure>.
StatusRequired
Datatypeteidata.xpath
Schematron
<sch:rule context="tei:citeStructure[not(parent::tei:citeStructure)]"> <sch:assert test="starts-with(@match,'/')">An XPath in @match on the outer <sch:name/> must start with '/'.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:citeStructure[parent::tei:citeStructure]"> <sch:assert test="not(starts-with(@match,'/'))">An XPath in @match must not start with '/' except on the outer <sch:name/>.</sch:assert> </sch:rule>
unit(unit) describes the structural unit indicated by the <citeStructure>.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
book
chapter
entry
poem
letter
line
section
verse
volume
Contained by
May contain
Example
<citeStructure unit="book"  match="//body/divuse="@n">  <citeStructure unit="chaptermatch="div"   use="position()delim=" ">   <citeStructure unit="versematch="div"    use="position()delim=":"/>  </citeStructure> </citeStructure>
Content model
<content>
 <sequence>
  <elementRef key="citeData" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="citeStructure"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element citeStructure
{
   tei_att.global.attributes,
   tei_att.citeStructurePart.attributes,
   attribute delim { text }?,
   attribute match { text },
   attribute unit { text }?,
   ( tei_citeData*, tei_citeStructure*, tei_model.descLike* )
}

1.46. <citedRange>

<citedRange> (cited range) defines the range of cited content, often represented by pages or other units [3.12.2.5. Scopes and Ranges in Bibliographic Citations]
Modulecore
Attributes
Member of
Contained by
May contain
Note

When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute may be used without to; for example a citation such as ‘p. 3ff’ might be encoded <citedRange from="3">p. 3ff</citedRange>.

Example
<citedRange>pp 12–13</citedRange> <citedRange unit="pagefrom="12to="13"/> <citedRange unit="volume">II</citedRange> <citedRange unit="page">12</citedRange>
Example
<bibl>  <ptr target="#mueller01"/>, <citedRange target="http://example.com/mueller3.xml#page4">vol. 3, pp.    4-5</citedRange> </bibl>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element citedRange
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.citing.attributes,
   tei_macro.phraseSeq
}

1.47. <classCode>

<classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the classification system in use, as defined by, e.g. a <taxonomy> element, or some other resource.
StatusRequired
Datatypeteidata.pointer
Contained by
core: imprint
header: textClass
May contain
Example
<classCode scheme="http://www.udc.org">410</classCode>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element classCode
{
   tei_att.global.attributes,
   attribute scheme { text },
   tei_macro.phraseSeq.limited
}

1.48. <classDecl>

<classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
header: taxonomy
Example
<classDecl>  <taxonomy xml:id="LCSH">   <bibl>Library of Congress Subject Headings</bibl>  </taxonomy> </classDecl> <!-- ... --> <textClass>  <keywords scheme="#LCSH">   <term>Political science</term>   <term>United States -- Politics and government —      Revolution, 1775-1783</term>  </keywords> </textClass>
Content model
<content>
 <elementRef key="taxonomy" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classDecl { tei_att.global.attributes, tei_taxonomy+ }

1.49. <classRef>

<classRef> points to the specification for an attribute or model class which is to be included in a schema [23.6. Class Specifications]
Moduletagdocs
Attributes
keythe identifier used for the required class within the source indicated.
StatusRequired
Datatypeteidata.xmlName
expandindicates how references to this class within a content model should be interpreted.
StatusOptional
Legal values are:
alternation
any one member of the class may appear
sequence
a single occurrence of all members of the class may appear in sequence
sequenceOptional
a single occurrence of one or more members of the class may appear in sequence
sequenceOptionalRepeatable
one or more occurrences of one or more members of the class may appear in sequence.
sequenceRepeatable
one or more occurrences of all members of the class may appear in sequence
Note

If the members of the class are a, b and c, then a reference to the class within a content model is understood as being a reference to a|b|c when expand is omitted or has the value alternation; to a,b,c when it has the value sequence; to (a?,b?,c?) when it has the value sequenceOptional; to (a*,b*,c*) when it has the value sequenceOptionalRepeatable; or to (a+,b+,c+) when it has the value sequenceRepeatable.

includesupplies a list of class members which are to be included in the schema being defined.
StatusOptional
Datatype0–∞ occurrences of teidata.xmlName separated by whitespace
exceptsupplies a list of class members which are to be excluded from the schema being defined.
StatusOptional
Datatype0–∞ occurrences of teidata.xmlName separated by whitespace
Member of
Contained by
May containEmpty element
Note

Attribute and model classes are identified by the name supplied as value for the ident attribute on the <classSpec> element in which they are declared. All TEI class names are unique; attribute class names conventionally begin with the letters att..

Example
<schemaSpec ident="myTEIestart="TEI">  <moduleRef key="tei"/>  <moduleRef key="core"   include="abbr add core addrLine address author bibl biblScope choice cit corr date del desc divGen editor emph expan foreign gap gloss graphic head hi index item l label lb lg list listBibl mentioned milestone name note num orig p pb ptr pubPlace publisher q ref reg relatedItem resp respStmt rs sic soCalled sp speaker stage teiCorpus term time title unclear"/>  <moduleRef key="header"   include="authority availability catRef category change classCode classDecl creation distributor edition editionStmt editorialDecl encodingDesc extent fileDesc funder idno keywords langUsage language licence notesStmt principal profileDesc projectDesc publicationStmt refsDecl revisionDesc samplingDecl seriesStmt sourceDesc sponsor taxonomy teiHeader textClass titleStmt"/>  <moduleRef key="textstructure"   include="TEI argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph front group opener postscript salute signed text titlePage titlePart trailer"/>  <classRef key="att.global.facs"/> </schemaSpec>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element classRef
{
   tei_att.global.attributes,
   tei_att.repeatable.attributes,
   attribute key { text },
   attribute expand
   {
      "alternation"
    | "sequence"
    | "sequenceOptional"
    | "sequenceOptionalRepeatable"
    | "sequenceRepeatable"
   }?,
   ( attribute include { list { * } }? | attribute except { list { * } }? ),
   empty
}

1.50. <classSpec>

<classSpec> (class specification) contains reference information for a TEI element class; that is a group of elements which appear together in content models, or which share some common attribute, or both. [23.3. Specification Elements 23.6. Class Specifications]
Moduletagdocs
Attributes
typeindicates whether this is a model class or an attribute class
Derived fromatt.typed
StatusRequired
Datatypeteidata.enumerated
Legal values are:
model
(content model) members of this class appear in the same content models
atts
(attributes) members of this class share common attributes
generateindicates which alternation and sequence instantiations of a model class may be referenced. By default, all variations are permitted.
StatusOptional
Datatype1–5 occurrences of teidata.enumerated separated by whitespace
Legal values are:
alternation
members of the class are alternatives
sequence
members of the class are to be provided in sequence
sequenceOptional
members of the class may be provided, in sequence, but are optional
sequenceOptionalRepeatable
members of the class may be provided one or more times, in sequence, but are optional.
sequenceRepeatable
members of the class may be provided one or more times, in sequence
Member of
Contained by
May contain
Example
<classSpec module="teitype="model"  ident="model.segLike">  <desc>groups elements used for arbitrary segmentation.</desc>  <classes>   <memberOf key="model.phrase"/>  </classes>  <remarks>   <p>The principles on which segmentation is carried out, and      any special codes or attribute values used, should be defined explicitly      in the <gi>segmentation</gi> element of the <gi>encodingDesc</gi> within      the associated TEI header.</p>  </remarks> </classSpec>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="classes" minOccurs="0"/>
  <elementRef key="constraintSpec"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="attList" minOccurs="0"/>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="listRef" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element classSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { "model" | "atts" },
   attribute generate
   {
      list
      {
         (
            "alternation"
          | "sequence"
          | "sequenceOptional"
          | "sequenceOptionalRepeatable"
          | "sequenceRepeatable"
         ),
         (
            "alternation"
          | "sequence"
          | "sequenceOptional"
          | "sequenceOptionalRepeatable"
          | "sequenceRepeatable"
         )?,
         (
            "alternation"
          | "sequence"
          | "sequenceOptional"
          | "sequenceOptionalRepeatable"
          | "sequenceRepeatable"
         )?,
         (
            "alternation"
          | "sequence"
          | "sequenceOptional"
          | "sequenceOptionalRepeatable"
          | "sequenceRepeatable"
         )?,
         (
            "alternation"
          | "sequence"
          | "sequenceOptional"
          | "sequenceOptionalRepeatable"
          | "sequenceRepeatable"
         )?
      }
   }?,
   (
      ( tei_model.identSynonyms | tei_model.descLike )*,
      tei_classes?,
      tei_constraintSpec*,
      tei_attList?,
      tei_exemplum*,
      tei_remarks*,
      tei_listRef*
   )
}

1.51. <classes>

<classes> (classes) specifies all the classes of which the documented element or class is a member or subclass. [23.5. Element Specifications 23.6. Class Specifications]
Moduletagdocs
Attributes
modespecifies the effect of this declaration on its parent module.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
change
this declaration changes the declaration of the same name in the current definition
replace
this declaration replaces the declaration of the same name in the current definition[Default]
Contained by
May contain
tagdocs: memberOf
Note

An empty <classes> element indicates that the element documented is not a member of any class. This should not generally happen.

Example
<classes>  <memberOf key="model.attributable"/>  <memberOf key="att.declarable"/> </classes>
This <classes> element indicates that the element documented (which may be an element or a class) is a member of two distinct classes: model.attributable and att.declarable.
Content model
<content>
 <elementRef key="memberOf" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element classes
{
   tei_att.global.attributes,
   attribute mode { "change" | "replace" }?,
   tei_memberOf*
}

1.52. <climate>

<climate> (climate) contains information about the physical climate of a place. [14.3.4.3. States, Traits, and Events]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<place xml:id="ROMA">  <placeName>Rome</placeName> <!-- ... -->  <climate>   <ab>    <table>     <head>24-hr Average Temperature</head>     <row>      <cell/>      <cell role="label">Jan</cell>      <cell role="label">Jun</cell>      <cell role="label">Dec</cell>     </row>     <row>      <cell role="label">°C</cell>      <cell role="data">7.1</cell>      <cell role="data">21.7</cell>      <cell role="data">8.3</cell>     </row>     <row>      <cell role="label">°F</cell>      <cell role="data">44.8</cell>      <cell role="data">71.1</cell>      <cell role="data">46.9</cell>     </row>    </table>   </ab>   <note>Taken from <bibl>     <abbr>GHCN 2 Beta</abbr>: The Global Historical Climatology Network,        version 2 beta, 1904 months between 1811 and 1980. <ptr target="http://www.worldclimate.com/cgi-bin/data.pl?ref=N41E012+1202+0004058G2"/>    </bibl>   </note>  </climate> </place>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
  </alternate>
  <elementRef key="climate" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element climate
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ ),
      ( tei_model.noteLike | tei_model.biblLike )*,
      tei_climate*
   )
}

1.53. <closer>

<closer> (closer) groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<div type="letter">  <p> perhaps you will favour me with a sight of it when convenient.</p>  <closer>   <salute>I remain, &amp;c. &amp;c.</salute>   <signed>H. Colburn</signed>  </closer> </div>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="signed"/>
  <elementRef key="dateline"/>
  <elementRef key="salute"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element closer
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_signed
    | tei_dateline
    | tei_salute
    | tei_model.phrase
    | tei_model.global
   )*
}

1.54. <code>

<code> contains literal code from some formal language such as a programming language. [23.1.1. Phrase Level Terms]
Moduletagdocs
Attributes
lang(formal language) a name identifying the formal language in which the code is expressed
StatusOptional
Datatypeteidata.word
Member of
Contained by
May containCharacter data only
Example
<code lang="JAVA"> Size fCheckbox1Size = new Size(); fCheckbox1Size.Height = 500; fCheckbox1Size.Width = 500; xCheckbox1.setSize(fCheckbox1Size); </code>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element code { tei_att.global.attributes, attribute lang { text }?, text }

1.55. <constraint>

<constraint> (constraint rules) the formal rules of a constraint [23.5. Element Specifications]
Moduletagdocs
Attributes
Contained by
May containANY
Example
<constraintSpec ident="isoconstraint"  scheme="schematron"    xmlns:sch="http://purl.oclc.org/dsdl/schematron">  <constraint>   <sch:rule context="tei:constraint">    <sch:assert test="tei:fileDesc/tei:titleStmt/tei:title[ @type eq 'main']">a main title must be supplied</sch:assert>   </sch:rule>  </constraint> </constraintSpec>
Example
<constraintSpec ident="local"  scheme="private">  <constraint>    (output = (ident(title) ident(author) "You must supply a title or an author"))  </constraint> </constraintSpec>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <anyElement/>
 </alternate>
</content>
    
Schema Declaration
element constraint
{
   tei_att.global.attributes,
   ( text | anyElement_constraint_4 )*
}

1.56. <constraintSpec>

<constraintSpec> (constraint on schema) contains a formal constraint, typically expressed in a rule-based schema language, to which a construct must conform in order to be considered valid [23.5. Element Specifications]
Moduletagdocs
Attributes
typecharacterizes the <constraintSpec> element in some sense; used to indicate when a <constraintSpec> warns about a deprecated construct.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
deprecationWarning
Indicates that this constraint specification warns that some other construct in the schema is deprecated.
schemesupplies the name of the language in which the constraints are defined
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:constraintSpec[ @mode = ('add','replace') or not( @mode ) ]"> <sch:assert test="@scheme">The @scheme attribute of <constraintSpec> is required when the @mode is <sch:value-of select="if (@mode) then concat('"',@mode,'"') else 'not specified'"/>.</sch:assert> </sch:rule>
Suggested values include:
schematron
(ISO Schematron)
Note

These Guidelines no longer recommend, and the current TEI stylesheets no longer support, the use of Schematron 1.x within <constraintSpec>. Thus the value schematron is used to indicate that ISO Schematron is used within the <constraintSpec>.

The scheme attribute is required when the value of mode is add or replace. The scheme attribute is permitted when the value of mode is delete, but these Guidelines make no reccomendation for what a processor should do if its value does not match that of the <constraintSpec> being deleted.

Member of
Contained by
May contain
Note

A child <constraint> is required when the mode attribute has the value replace or add (or is not specified, as add is the default). No child elements are permitted when the mode attribute has the value delete. At least one child element is required when the mode attribute has the value change.

ExampleThis constraint uses Schematron to enforce the presence of the spanTo attribute (which comes from an attribute class) on the <addSpan> element:
<constraintSpec ident="demo-c1"  scheme="schematron"    xmlns:sch="http://purl.oclc.org/dsdl/schematron">  <desc>Enforce the presence of the <att>spanTo</att> attribute</desc>  <constraint>   <sch:rule context="tei:addSpan">    <sch:assert test="@spanTo">The spanTo= attribute of <sch:name/> is required.</sch:assert>   </sch:rule>  </constraint> </constraintSpec>
Example
<constraintSpec ident="demo-c2"  scheme="schematron"    xmlns:sch="http://purl.oclc.org/dsdl/schematron">  <desc>Implement an accessibility rule which says that pictures    should have textual explanations</desc>  <constraint>   <sch:rule context="tei:figure">    <sch:report test="not( tei:figDesc | tei:head )">You should        provide information in a figure from which        we can construct an alt attribute in HTML</sch:report>   </sch:rule>  </constraint> </constraintSpec>
ExampleThis constraint uses SPITBOL (a language which is not expressed in XML) to check whether the title and author are identical:
<constraintSpec ident="author_ne_title"  scheme="SPITBOL">  <constraint>    (output = leq(title,author) "title and author cannot be the same")  </constraint> </constraintSpec>
Schematron
<sch:rule context="tei:constraintSpec[ @mode eq 'delete']"> <sch:report test="child::*">This constraintSpec element has a mode= of "delete" even though it has child elements. Change the mode= to "add", "change", or "replace", or remove the child elements.</sch:report> </sch:rule> <sch:rule context="tei:constraintSpec[ @mode eq 'change']"> <sch:assert test="child::*">This constraintSpec element has a mode= of "change", but does not have any child elements. Specify child elements, or change the mode= to "delete".</sch:assert> </sch:rule> <sch:rule context="tei:constraintSpec[ @mode = ('add','replace') ]"> <sch:assert test="child::tei:constraint">This constraintSpec element has a mode= of "<sch:value-of select="@mode"/>", but does not have a child 'constraint' element. Use a child 'constraint' element or change the mode= to "delete" or "change".</sch:assert> </sch:rule>
SchematronRelationship between scheme attribute and contents: Schematron 1.x
<sch:rule context="tei:constraintSpec"> <sch:report test="tei:constraint/sch1x:* and @scheme = ('isoschematron','schematron')">Rules in the Schematron 1.* language must be inside a constraintSpec with a value other than 'schematron' or 'isoschematron' on the scheme attribute</sch:report> </sch:rule>
SchematronRelationship between scheme attribute and contents: ISO Schematron
<sch:rule context="tei:constraintSpec[ @mode = ('add','replace') or not( @mode ) ]"> <sch:report test="tei:constraint/sch:* and not( @scheme eq 'schematron')">Rules in the ISO Schematron language must be inside a constraintSpec with the value 'schematron' on the scheme attribute</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:constraintSpec[ @scheme eq 'schematron']/tei:constraint[ .//sch:assert | .//sch:report ]"> <sch:let name="assertsHaveContext"  value="for $a in .//sch:assert return exists( $a/ancestor::sch:rule/@context )"/> <sch:let name="reportsHaveContext"  value="for $r in .//sch:report return exists( $r/ancestor::sch:rule/@context )"/> <sch:report test="( $assertsHaveContext, $reportsHaveContext ) = false()"  role="warning">The use of an <sch:assert> or <sch:report> that does not have a context (i.e., does not have an ancestor <sch:rule> with a @context attribute) in an ISO Schematron constraint specification is deprecated, and will become invalid after 2025-03-15.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:constraintSpec[ @mode eq 'add' or not( @mode ) ]"> <sch:let name="myIdent"  value="normalize-space(@ident)"/> <sch:report test="preceding::tei:constraintSpec[ normalize-space(@ident) eq $myIdent ]"> The @ident of 'constraintSpec' should be unique; this one (<sch:value-of select="$myIdent"/>) is the same as that of a previous 'constraintSpec'. </sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="constraint"
   minOccurs="0" maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element constraintSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { "deprecationWarning" }?,
   attribute scheme { "schematron" }?,
   ( ( tei_model.identSynonyms | tei_model.descLike )*, tei_constraint? )
}

1.57. <content>

<content> (content model) contains a declaration of the intended content model for the element (or other construct) being specified. [23.5. Element Specifications]
Moduletagdocs
Attributes
autoPrefixcontrols whether or not pattern names generated in the corresponding RELAX NG schema source are automatically prefixed to avoid potential nameclashes.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
Each name referenced in e.g. an <rng:ref> element within a content model is automatically prefixed by the value of the prefix attribute on the current <schemaSpec>[Default]
false
No prefixes are added: any prefix required by the value of the prefix attribute on the current <schemaSpec> must therefore be supplied explicitly, as appropriate.
Contained by
May containANY
Note

It is required that the <content> element has only one child element. If several RELAX NG elements are desired, they must be wrapped in a <rng:div>.

ExampleThis sample <content> element indicates that the element being specified has no content:
<content>  <empty/> </content>
ExampleThis <content> element defines a content model, expressed directly in the TEI ODD language, that allows either a sequence of paragraphs or a series of <msItem> elements optionally preceded by a <summary>:
<content>  <alternate>   <classRef key="model.pLike"    maxOccurs="unbounded"/>   <sequence>    <elementRef key="summaryminOccurs="0"     maxOccurs="1"/>    <elementRef key="msItem"     maxOccurs="unbounded"/>   </sequence>  </alternate> </content>
ExampleThis sample <content> element defines a content model, expressed in the RELAX NG schema language, that allows either a sequence of paragraphs or a series of <msItem> elements optionally preceded by a <summary>:
<content>  <rng:choice>   <rng:oneOrMore>    <rng:ref name="model.pLike"/>   </rng:oneOrMore>   <rng:group>    <rng:optional>     <rng:ref name="summary"/>    </rng:optional>    <rng:oneOrMore>     <rng:ref name="msItem"/>    </rng:oneOrMore>   </rng:group>  </rng:choice> </content>
Content model
<content>
 <alternate>
  <elementRef key="valList" minOccurs="1"
   maxOccurs="1"/>
  <classRef key="model.contentPart"
   minOccurs="1" maxOccurs="1"/>
  <anyElement minOccurs="1" maxOccurs="1"
   require="http://relaxng.org/ns/compatibility/annotations/1.0 http://relaxng.org/ns/structure/1.0"/>
 </alternate>
</content>
    
Schema Declaration
element content
{
   tei_att.global.attributes,
   attribute autoPrefix { "true" | "false" }?,
   ( tei_valList | tei_model.contentPart | anyElement_content_3 )
}

1.58. <conversion>

<conversion> defines how to calculate one unit of measure in terms of another. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
fromUnitindicates a source unit of measure that is to be converted into another unit indicated in toUnit.
StatusRequired
Datatypeteidata.pointer
toUnitthe target unit of measurement for a conversion from a source unit referenced in fromUnit.
StatusRequired
Datatypeteidata.pointer
Contained by
header: unitDef
May containEmpty element
Note

The conversion element is designed to store information about converting from one unit of measurement to another. The formula attribute holds an XPath expression that indicates how the measurement system in fromUnit is converted to the system in toUnit. Do not confuse the usage of the dating attributes (from and to) in the examples with the attributes (fromUnit and toUnit) designed to reference units of measure.

Example
<conversion fromUnit="#shilling"  toUnit="#penceformula="$fromUnit * 12from="1707"  to="1971"/>
Example
<conversion fromUnit="#pound"  toUnit="#shillingformula="$fromUnit * 20from="1701"  to="1971"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element conversion
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.formula.attributes,
   tei_att.locatable.attributes,
   attribute calendar { list { + } }?,
   attribute fromUnit { text },
   attribute toUnit { text },
   empty
}

1.59. <corr>

<corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone:
I don't know, Juan. It's so far in the past now — how <corr>can we</corr> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element corr
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.60. <correction>

<correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
statusindicates the degree of correction applied to the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
high
the text has been thoroughly checked and proofread.
medium
the text has been checked at least once.
low
the text has not been checked.
unknown
the correction status of the text is unknown.
methodindicates the method adopted to indicate corrections within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
corrections have been made silently[Default]
markup
corrections have been represented using markup
Member of
Contained by
May contain
core: p
Note

May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.5. Simple Editorial Changes.

Example
<correction>  <p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user    defined dictionary of 500 extra words taken from Chambers Twentieth Century    Dictionary.</p> </correction>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correction
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute status { "high" | "medium" | "low" | "unknown" }?,
   attribute method { "silent" | "markup" }?,
   tei_model.pLike+
}

1.61. <correspAction>

<correspAction> (correspondence action) contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
typedescribes the nature of the action.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
sent
information concerning the sending or dispatch of a message.
received
information concerning the receipt of a message.
transmitted
information concerning the transmission of a message, i.e. between the dispatch and the next receipt, redirect or forwarding.
redirected
information concerning the redirection of an unread message.
forwarded
information concerning the forwarding of a message.
Member of
Contained by
header: correspDesc
May contain
Example
<correspAction type="sent">  <persName>Adelbert von Chamisso</persName>  <settlement>Vertus</settlement>  <date when="1807-01-29"/> </correspAction>
Content model
<content>
 <alternate>
  <classRef key="model.correspActionPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspAction
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.sortable.attributes,
   attribute type
   {
      "sent" | "received" | "transmitted" | "redirected" | "forwarded"
   }?,
   ( tei_model.correspActionPart+ | tei_model.pLike+ )
}

1.62. <correspContext>

<correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
Contained by
header: correspDesc
May contain
tagdocs: listRef
Example
<correspContext>  <ptr type="nextsubtype="toAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>  <ptr type="prevsubtype="fromAuthor"   target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/> </correspContext>
Example
<correspContext>  <ref type="prev"   target="http://weber-gesamtausgabe.de/A040962"> Previous letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1816-12-30">December 30, 1816</date>  </ref>  <ref type="next"   target="http://weber-gesamtausgabe.de/A041003"> Next letter of  <persName>Carl Maria von Weber</persName> to  <persName>Caroline Brandt</persName>:  <date when="1817-01-05">January 5, 1817</date>  </ref> </correspContext>
Content model
<content>
 <classRef key="model.correspContextPart"
  minOccurs="1" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element correspContext
{
   tei_att.global.attributes,
   tei_model.correspContextPart+
}

1.63. <correspDesc>

<correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence. [2.4.6. Correspondence Description]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
Example
<correspDesc>  <correspAction type="sent">   <persName>Carl Maria von Weber</persName>   <settlement>Dresden</settlement>   <date when="1817-06-23">23 June 1817</date>  </correspAction>  <correspAction type="received">   <persName>Caroline Brandt</persName>   <settlement>Prag</settlement>  </correspAction>  <correspContext>   <ref type="prev"    target="http://www.weber-gesamtausgabe.de/A041209">Previous letter of   <persName>Carl Maria von Weber</persName>      to <persName>Caroline Brandt</persName>:   <date from="1817-06-19to="1817-06-20">June 19/20, 1817</date>   </ref>   <ref type="next"    target="http://www.weber-gesamtausgabe.de/A041217">Next letter of   <persName>Carl Maria von Weber</persName> to   <persName>Caroline Brandt</persName>:   <date when="1817-06-27">June 27, 1817</date>   </ref>  </correspContext> </correspDesc>
Content model
<content>
 <alternate>
  <classRef key="model.correspDescPart"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element correspDesc
{
   tei_att.declarable.attributes,
   tei_att.canonical.attributes,
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( tei_model.correspDescPart+ | tei_model.pLike+ )
}

1.64. <country>

<country> (country) contains the name of a geo-political unit, such as a nation, country, colony, or commonwealth, larger than or administratively superior to a region and smaller than a bloc. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

The recommended source for codes to represent coded country names is ISO 3166.

Example
<country key="DK">Denmark</country>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element country
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.65. <creation>

<creation> (creation) contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
header: profileDesc
May contain
Note

The <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.

It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication.

Example
<creation>  <date>Before 1987</date> </creation>
Example
<creation>  <date when="1988-07-10">10 July 1988</date> </creation>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <elementRef key="listChange"/>
 </alternate>
</content>
    
Schema Declaration
element creation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   ( text | tei_model.limitedPhrase | tei_listChange )*
}

1.66. <dataFacet>

<dataFacet> Restricts the value of the strings used to represent values of a datatype, according to XML Schema Part 2: Datatypes Second Edition. [23.5.3.1. Datatypes]
Moduletagdocs
Attributes
namethe name of the facet.
StatusRequired
Datatypeteidata.word
Legal values are:
length
minLength
maxLength
pattern
enumeration
whiteSpace
maxInclusive
minInclusive
maxExclusive
minExclusive
totalDigits
fractionDigits
valuethe facet value.
StatusRequired
Datatypestring
Contained by
tagdocs: dataRef
May containEmpty element
Note

This element is only allowed when the parent <dataRef> refers with name to a datatype from the specification XML Schema Part 2: Datatypes Second Edition.

Example
<datatype>  <dataRef name="decimal">   <dataFacet name="maxInclusive"    value="360.0"/>   <dataFacet name="minInclusive"    value="-360.0"/>  </dataRef> </datatype>
Example
<dataSpec ident="data.integerExample">  <desc>datatype used for attributes taking an integer value between 0 and 99</desc>  <content>   <dataRef name="nonNegativeInteger">    <dataFacet name="maxInclusive"     value="99"/>    <dataFacet name="minInclusivevalue="0"/>   </dataRef>  </content> </dataSpec>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element dataFacet
{
   tei_att.global.attributes,
   attribute name
   {
      "length"
    | "minLength"
    | "maxLength"
    | "pattern"
    | "enumeration"
    | "whiteSpace"
    | "maxInclusive"
    | "minInclusive"
    | "maxExclusive"
    | "minExclusive"
    | "totalDigits"
    | "fractionDigits"
   },
   attribute value { text },
   empty
}

1.67. <dataRef>

<dataRef> identifies the datatype of an attribute value, either by referencing an item in an externally defined datatype library, or by pointing to a TEI-defined data specification [23.5.3.1. Datatypes]
Moduletagdocs
Attributes
keythe identifier used for this datatype specification
StatusOptional
Datatypeteidata.xmlName
namethe name of a datatype in the list provided by XML Schema Part 2: Datatypes Second Edition
StatusOptional
Datatypeteidata.xmlName
refa pointer to a datatype defined in some datatype library
StatusOptional
Datatypeteidata.pointer
restrictionsupplies a string representing a regular expression providing additional constraints on the strings used to represent values of this datatype
StatusOptional
Datatypeteidata.pattern
Member of
Contained by
May contain
tagdocs: dataFacet
Note

Only one of the attributes key, name, and ref may be used on any given instance of <dataRef>.

Neither a restriction attribute nor a <dataFacet> child element may be used unless the <dataRef> refers to a datatype from the specification XML Schema Part 2: Datatypes Second Edition with a name attribute.

Example
<schemaSpec ident="myTEI"  source="http://www.tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.xml"> <!-- ... -->  <dataRef key="teidata.enumerated"/> <!-- ... --> </schemaSpec>
Example
<schemaSpec ident="myTEI"  source="http://www.tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.xml"> <!-- ... -->  <dataRef name="float"/> <!-- ... --> </schemaSpec>
Example
<dataSpec ident="data.integerExample">  <desc>datatype used for attributes taking an integer value between 0 and 99</desc>  <content>   <dataRef name="nonNegativeInteger"    restriction="[0-9][0-9]?"/>  </content> </dataSpec>
Schematron
<sch:rule context="tei:dataRef[tei:dataFacet]"> <sch:assert test="@name" role="nonfatal">Data facets can only be specified for references to datatypes specified by XML Schema Part 2: Datatypes Second Edition — that is, for there to be a 'dataFacet' child there must be a @name attribute.</sch:assert> <sch:report test="@restriction"  role="nonfatal">Data facets and restrictions cannot both be expressed on the same data reference — that is, the @restriction attribute cannot be used when a 'dataFacet' element is present.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:dataRef[@restriction]"> <sch:assert test="@name" role="nonfatal">Restrictions can only be specified for references to datatypes specified by XML Schema Part 2: Datatypes Second Edition — that is, for there to be a @restriction attribute there must be a @name attribute, too.</sch:assert> </sch:rule>
Content model
<content>
 <elementRef minOccurs="0"
  maxOccurs="unbounded" key="dataFacet"/>
</content>
    
Schema Declaration
element dataRef
{
   tei_att.global.attributes,
   (
      attribute key { text }?
    | attribute name { text }?
    | attribute ref { text }?
   ),
   attribute restriction { text }?,
   tei_dataFacet*
}

1.68. <dataSpec>

<dataSpec> (datatype specification) documents a datatype. [23.3. Specification Elements 23.7. Macro Specifications]
Moduletagdocs
Attributes
Member of
Contained by
May contain
Example
<dataSpec ident="teidata.pointer">  <desc versionDate="2013-01-19"   xml:lang="en">defines the range of    attribute values used to provide a single URI, absolute or relative,    pointing to some other resource, either within the current document    or elsewhere.</desc>  <content>   <dataRef name="anyURI"/>  </content> </dataSpec>
Schematron
<sch:rule role="warn"  context="tei:dataSpec/tei:content"> <sch:report test=".//tei:anyElement | .//tei:classRef | .//tei:elementRef"> A datatype specification should not refer to an element or a class. </sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <elementRef key="content"/>
   <elementRef key="valList"/>
  </alternate>
  <elementRef key="constraintSpec"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="listRef" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element dataSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   (
      ( tei_model.identSynonyms | tei_model.descLike )*,
      ( tei_content | tei_valList )?,
      tei_constraintSpec*,
      tei_exemplum*,
      tei_remarks*,
      tei_listRef*
   )
}

1.69. <datatype>

<datatype> (datatype) specifies the declared value for an attribute, by referring to any datatype defined by the chosen schema language. [1.4.2. Datatype Specifications 23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
minOccurs(minimum number of occurences) indicates the minimum number of times this datatype may occur in an instance of the attribute being defined
Derived fromatt.repeatable
StatusOptional
Datatypeteidata.count
Default1
maxOccurs(maximum number of occurences) indicates the maximum number of times this datatype may occur in an instance of the attribute being defined
Derived fromatt.repeatable
StatusOptional
Datatypeteidata.unboundedCount
Default1
Contained by
tagdocs: attDef
May containANY
Note

In the TEI scheme, most datatypes are expressed using pre-defined TEI macros, which map a name in the form teidata.xxxx to a datatype defined by RELAX NG or the W3C Schema Language.

Example
<datatype>  <dataRef name="token"/> </datatype>
Example
<datatype>  <dataRef key="teidata.enumerated"/> </datatype>
ExampleThe encoding in the following example requires that the attribute being defined contain at least two URIs in its value, as is the case for the target attribute of <join>.
<datatype minOccurs="2"  maxOccurs="unbounded">  <dataRef key="teidata.pointer"/> </datatype>
Content model
<content>
 <alternate>
  <elementRef key="dataRef"/>
  <anyElement require="http://relaxng.org/ns/structure/1.0"/>
 </alternate>
</content>
    
Schema Declaration
element datatype
{
   tei_att.global.attributes,
   attribute minOccurs { text }?,
   attribute maxOccurs { text }?,
   ( tei_dataRef | anyElement_datatype_5 )
}

1.70. <date>

<date> (date) contains a date in any format. [3.6.4. Dates and Times 2.2.4. Publication, Distribution, Licensing, etc. 2.6. The Revision Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 16.2.3. The Setting Description 14.4. Dates]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<date when="1980-02">early February 1980</date>
Example
Given on the <date when="1977-06-12">Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
Example
<date when="1990-09">September 1990</date>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element date
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.71. <dateline>

<dateline> (dateline) contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<dateline>Walden, this 29. of August 1592</dateline>
Example
<div type="chapter">  <p> <!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>  <closer>   <dateline>    <name type="place">Trieste-Zürich-Paris,</name>    <date>1914–1921</date>   </dateline>  </closer> </div>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
  <elementRef key="docDate"/>
 </alternate>
</content>
    
Schema Declaration
element dateline
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.global
    | tei_docDate
   )*
}

1.72. <death>

<death> (death) contains information about a person's death, such as its date and place. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
proclaimed
assumed
verified
clinical
brain
natural
unnatural
fragmentation
dissolution
Note

This attribute is not intended to express the cause of death.

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<death when="1902-10-01"/>
Example
<death when="1960-12-10">Passed away near <name type="place">Aix-la-Chapelle</name>, after suffering from cerebral palsy. </death>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element death
{
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.73. <defaultVal>

<defaultVal> (default value) specifies the default declared value for an attribute. [23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
Contained by
tagdocs: attDef
May containCharacter data only
Note

any legal declared value or TEI-defined keyword

Example
<defaultVal>#IMPLIED</defaultVal>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element defaultVal
{
   tei_att.global.attributes,
   tei_att.combinable.attributes,
   text
}

1.74. <del>

<del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way.

Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 22. Certainty, Precision, and Responsibility).

There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 12.3.1.7. Text Omitted from or Supplied in the Transcription and 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription.

Example
<l>  <del rend="overtyped">Mein</del> Frisch <del rend="overstriketype="primary">schwebt</del> weht der Wind </l>
Example
<del rend="overstrike">  <gap reason="illegiblequantity="5"   unit="character"/> </del>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element del
{
   tei_att.global.attributes,
   tei_att.transcriptional.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.75. <desc>

<desc> (description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented. [23.4.1. Description of Components]
Modulecore
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
deprecationInfo
(deprecation information) This element describes why or how its parent element is being deprecated, typically including recommendations for alternate encoding.
<dataSpec module="tei"  ident="teidata.point"  validUntil="2050-02-25">  <desc type="deprecationInfo"   versionDate="2018-09-14"   xml:lang="en">Several standards bodies, including NIST in the USA,    strongly recommend against ending the representation of a number    with a decimal point. So instead of <q>3.</q> use either <q>3</q>    or <q>3.0</q>.</desc> <!-- ... --> </dataSpec>
Member of
Contained by
May contain
Note

When used in a specification element such as <elementSpec>, TEI convention requires that this be expressed as a finite clause, begining with an active verb.

ExampleExample of a <desc> element inside a documentation element.
<dataSpec module="tei"  ident="teidata.point">  <desc versionDate="2010-10-17"   xml:lang="en">defines the data type used to express a point in cartesian space.</desc>  <content>   <dataRef name="token"    restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>  </content> <!-- ... --> </dataSpec>
ExampleExample of a <desc> element in a non-documentation element.
<place xml:id="KERG2">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
SchematronA <desc> with a type of deprecationInfo should only occur when its parent element is being deprecated. Furthermore, it should always occur in an element that is being deprecated when <desc> is a valid child of that element.
<sch:rule context="tei:desc[ @type eq 'deprecationInfo']"> <sch:assert test="../@validUntil">Information about a deprecation should only be present in a specification element that is being deprecated: that is, only an element that has a @validUntil attribute should have a child <desc type="deprecationInfo">.</sch:assert> </sch:rule>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element desc
{
   tei_att.global.attributes,
   tei_att.translatable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { "deprecationInfo" }?,
   tei_macro.limitedContent
}

1.76. <distinct>

<distinct> identifies any word or phrase which is regarded as linguistically distinct, for example as archaic, technical, dialectal, non-preferred, etc., or as forming part of a sublanguage. [3.3.2.3. Other Linguistically Distinct Material]
Modulecore
Attributes
typespecifies the sublanguage or register to which the word or phrase is being assigned
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
timespecifies how the phrase is distinct diachronically
StatusOptional
Datatypeteidata.text
spacespecifies how the phrase is distinct diatopically
StatusOptional
Datatypeteidata.text
socialspecifies how the phrase is distinct diastratically
StatusOptional
Datatypeteidata.text
Member of
Contained by
May contain
Example
Next morning a boy in that dormitory confided to his bosom friend, a <distinct type="ps_slang">fag</distinct> of Macrea's, that there was trouble in their midst which King <distinct type="archaic">would fain</distinct> keep secret.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distinct
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute time { text }?,
   attribute space { text }?,
   attribute social { text }?,
   tei_macro.phraseSeq
}

1.77. <distributor>

<distributor> (distributor) supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<distributor>Oxford Text Archive</distributor> <distributor>Redwood and Burn Ltd</distributor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element distributor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq
}

1.78. <district>

<district> (district) contains the name of any kind of subdivision of a settlement, such as a parish, ward, or other administrative or geographic unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <district type="ward">Jericho</district>  <settlement>Oxford</settlement> </placeName>
Example
<placeName>  <district type="area">South Side</district>  <settlement>Chicago</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element district
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.79. <div>

<div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back body div front
May contain
Example
<body>  <div type="part">   <head>Fallacies of Authority</head>   <p>The subject of which is Authority in various shapes, and the object, to repress all      exercise of the reasoning faculty.</p>   <div n="1type="chapter">    <head>The Nature of Authority</head>    <p>With reference to any proposed measures having for their object the greatest        happiness of the greatest number [...]</p>    <div n="1.1type="section">     <head>Analysis of Authority</head>     <p>What on any given occasion is the legitimate weight or influence to be attached to          authority [...] </p>    </div>    <div n="1.2type="section">     <head>Appeal to Authority, in What Cases Fallacious.</head>     <p>Reference to authority is open to the charge of fallacy when [...] </p>    </div>   </div>  </div> </body>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:l or ancestor::tei:lg) and not(ancestor::tei:floatingText)"> Abstract model violation: Lines may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:div"> <sch:report test="(ancestor::tei:p or ancestor::tei:ab) and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div, unless div is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.divLike"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.divLike"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   tei_att.written.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.divLike | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.divLike | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.80. <div1>

<div1> (level-1 text division) contains a first-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back body front
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div1 xml:id="levin="Itype="part">  <head>Part I: Of Man </head>  <div2 xml:id="levi1n="1type="chapter">   <head>Chap. I. Of Sense </head>   <p>Concerning the Thoughts of man... </p>  </div2> </div1> <div1 xml:id="leviin="IItype="part">  <head>Part II: Of Common-Wealth</head> </div1>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div2Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div2Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div1
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div2Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div2Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.81. <div2>

<div2> (level-2 text division) contains a second-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div1
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div1 n="2type="part">  <head>The Second Partition:    The Cure of Melancholy</head>  <div2 n="2.1type="section">   <div3 n="2.1.1type="member">    <div4 n="2.1.1.1type="subsection">     <head>Unlawful Cures rejected.</head>     <p>Inveterate melancholy, howsoever it may seem to          be a continuate, inexorable disease, hard to be          cured, accompanying them to their graves most part          (as <ref target="#a">Montanus</ref> observes), yet many          times it may be helped...     </p>    </div4>   </div3>  </div2>  <div2 n="2.2type="section">   <div3 n="2.2.1type="member">    <head>Sect. II. Memb. I</head>    <p/>   </div3>  </div2>  <div2 n="2.3type="section">   <div3 n="2.3.1type="member">    <head>Sect. III. Memb. I</head>    <p/>   </div3>  </div2> </div1>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div3Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div3Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div2
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div3Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div3Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.82. <div3>

<div3> (level-3 text division) contains a third-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div2
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div2 n="2.2type="section">  <div3 n="2.2.1type="member">   <head>Sect. II. Memb. I</head>   <p/>  </div3>  <div3 n="2.2.2type="member">   <head>Memb. II Retention and Evacuation rectified.</head>   <p/>  </div3>  <div3 n="2.2.3type="member">   <head>Memb. III Ayr rectified. With a digression of the Ayr.</head>   <p/>  </div3> </div2>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div4Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div4Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div3
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div4Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div4Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.83. <div4>

<div4> (level-4 text division) contains a fourth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div3
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div3 n="2.2.1type="member">  <head>Sect. II. Memb. I</head>  <div4 n="2.2.1.1type="subsection">   <head>Subsect I. — Dyet rectified in substance.</head>   <p>Diet, <term xml:lang="grc">diaitotiku</term>, <term xml:lang="la">victus</term> or      living </p>  </div4>  <div4 n="2.2.2.1type="subsection">   <head>Subsect II. — Dyet rectified in quantity.</head>   <p>Man alone, saith Cardan, eates and drinks without appetite, and useth all his pleasures      without necessity </p>  </div4> </div3>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div5Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div5Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div4
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div5Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div5Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.84. <div5>

<div5> (level-5 text division) contains a fifth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div4
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div2 type="chapter">  <head>Recipes</head>  <head>Chapter VI.</head>  <div3>   <head>Fruit and vegetable soups</head>   <p>...</p>   <div4>    <head>Stocks for all kinds of soups</head>    <div5 type="recipe">     <head>Rich strong stock</head> <!-- ... -->    </div5>    <div5 type="recipe">     <head>Medium Stock</head> <!-- ... -->    </div5>   </div4>   <div4 type="recipe">    <head>Apple soup</head>    <div5>     <head>Ingredients</head>     <list>      <item>2 lbs. of good boiling apples,</item>      <item>3/4 teaspoonful of white pepper,</item>      <item>6 cloves,</item>      <item>cayenne or ginger to taste,</item>      <item>3 quarts of medium stock</item>     </list>    </div5>    <div5>     <head>Mode</head>     <p>Peel and quarter the apples taking out their cores; put them into          the stock, stew them gently till tender, Rub the whole through a          strainer, add the seasoning. give it one boil up, and serve.</p>    </div5>    <div5>     <head>Time</head>     <p>1 hour.</p>    </div5>    <div5>     <head>Average cost</head>     <p>per quart, 1s.</p>    </div5>    <div5>     <head>Seasonable</head>     <p>from September to December.</p>    </div5>    <div5>     <head>Sufficient</head>     <p> for 10 persons</p>    </div5>    <div5>     <head>The apple</head>     <p>This useful fruit is mentioned in Holy Writ; and Homer describes it          as valuable in his time... As a food, the apple cannot be considered          to rank high, as more than the half of it consists of water, and          the rest of its properties are not the most nourishing. It is          however a useful adjunct to other kinds of food, and, when cooked, is          esteemed as slightly laxative.</p>    </div5>   </div4>   <div4 type="recipe">    <head>Artichoke (Jerusalem) soup</head>    <p>...</p>   </div4> <!-- other recipes here -->  </div3> </div2>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div6Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div6Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div5
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div6Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div6Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.85. <div6>

<div6> (level-6 text division) contains a sixth-level subdivision of the front, body, or back of a text. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div5
May contain
Note

any sequence of low-level structural elements, possibly grouped into lower subdivisions.

Example
<div2 type="chapter">  <head>Recipes</head>  <head>Chapter VI.</head>  <div3>   <head>Fruit and vegetable soups</head>   <p>...</p>   <div4>    <head>Stocks for all kinds of soups</head>    <div5 type="recipe">     <head>Rich strong stock</head>     <div6>      <head>Ingredients</head>      <list>       <item>4 lbs of shin of beef,</item>       <item>4 lbs of knuckle of veal,</item> <!-- ... -->       <item>4 quarts of water</item>      </list>     </div6>     <div6>      <head>Mode</head>      <p>Line a delicately clean stewpan... Strain through a very            fine hair sieve, or tammy, and it will be fit for use</p>     </div6>     <div6>      <head>Time</head>      <p>5 hours.</p>     </div6>     <div6>      <head>Average cost</head>      <p>1s 3d. per quart</p>     </div6>    </div5>    <div5 type="recipe">     <head>Medium Stock</head> <!-- ... -->    </div5>   </div4> <!-- ... -->  </div3> </div2>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <alternate>
      <classRef key="model.div7Like"/>
      <classRef key="model.divGenLike"/>
     </alternate>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
    <sequence>
     <sequence minOccurs="1"
      maxOccurs="unbounded">
      <alternate minOccurs="1"
       maxOccurs="1">
       <elementRef key="schemaSpec"/>
       <classRef key="model.common"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
     <sequence minOccurs="0"
      maxOccurs="unbounded">
      <alternate>
       <classRef key="model.div7Like"/>
       <classRef key="model.divGenLike"/>
      </alternate>
      <classRef key="model.global"
       minOccurs="0" maxOccurs="unbounded"/>
     </sequence>
    </sequence>
   </alternate>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div6
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            (
               (
                  (
                     ( tei_model.div7Like | tei_model.divGenLike ),
                     tei_model.global*
                  )+
               )
             | (
                  (
                     (
                        ( tei_schemaSpec | tei_model.common ),
                        tei_model.global*
                     )+
                  ),
                  (
                     (
                        ( tei_model.div7Like | tei_model.divGenLike ),
                        tei_model.global*
                     )*
                  )
               )
            ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.86. <div7>

<div7> (level-7 text division) contains the smallest possible subdivision of the front, body or back of a text, larger than a paragraph. [4.1.2. Numbered Divisions]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: div6
May contain
Note

any sequence of low-level structural elements, e.g., paragraphs (<p>), lists (<list>), or examples (<eg> or <egXML>).

Example
<div2 type="chapter">  <head>Recipes</head>  <head>Chapter VI.</head>  <div3>   <head>Fruit and vegetable soups</head>   <p>...</p>   <div4>    <head>Stocks for all kinds of soups</head>    <div5 type="recipe">     <head>Asparagus soup</head>     <div6 type="altRecipe">      <head>I.</head>      <div7>       <head>Ingredients</head>       <list>        <item> ...</item>       </list>      </div7>      <div7>       <head>Mode</head>       <p>Put the beef, cut into pieces and rolled in flour, into a              stewpan...</p>      </div7> <!-- ... -->     </div6>     <div6 type="altRecipe">      <head>II.</head>      <div7>       <head>Ingredients</head>       <list>        <item> ...</item>       </list>      </div7>      <div7>       <head>Mode</head>       <p>Boil the peas, and rub them through a sieve; add the gravy...</p>      </div7>     </div6>    </div5>   </div4>  </div3> </div2>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <alternate minOccurs="1" maxOccurs="1">
     <elementRef key="schemaSpec"/>
     <classRef key="model.common"/>
    </alternate>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.divBottom"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element div7
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         (
            ( ( ( tei_schemaSpec | tei_model.common ), tei_model.global* )+ ),
            ( ( tei_model.divBottom, tei_model.global* )* )
         )?
      )
   )
}

1.87. <divGen>

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2. Index Entries]
Modulecore
Attributes
typespecifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
index
an index is to be generated and inserted at this point.
toc
a table of contents
figlist
a list of figures
tablist
a list of tables
Note

Valid values are application-dependent; those shown are of obvious utility in document production, but are by no means exhaustive.

Member of
Contained by
May contain
core: head
Note

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.

ExampleOne use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on <index> elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:
<back>  <div1 type="backmat">   <head>Bibliography</head> <!-- ... -->  </div1>  <div1 type="backmat">   <head>Indices</head>   <divGen n="Index Nominumtype="NAMES"/>   <divGen n="Index Rerumtype="THINGS"/>  </div1> </back>
ExampleAnother use for <divGen> is to specify the location of an automatically produced table of contents:
<front> <!--<titlePage>...</titlePage>-->  <divGen type="toc"/>  <div>   <head>Preface</head>   <p> ... </p>  </div> </front>
Content model
<content>
 <classRef key="model.headLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element divGen
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   tei_model.headLike*
}

1.88. <docAuthor>

<docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

The document author's name often occurs within a byline, but the <docAuthor> element may be used whether the <byline> element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with <byline> without <docAuthor>.)

Example
<titlePage>  <docTitle>   <titlePart>Travels into Several Remote Nations of the World, in Four      Parts.</titlePart>  </docTitle>  <byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon,    and then a Captain of several Ships</byline> </titlePage>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docAuthor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.89. <docDate>

<docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

Cf. the general <date> element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it.

Example
<docImprint>Oxford, Clarendon Press, <docDate>1987</docDate> </docImprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element docDate
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_att.datable.attributes,
   tei_att.calendarSystem.attributes,
   tei_macro.phraseSeq
}

1.90. <docEdition>

<docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Note

Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element.

Example
<docEdition>The Third edition Corrected</docEdition>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element docEdition { tei_att.global.attributes, tei_macro.paraContent }

1.91. <docImprint>

<docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Note

Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often.

Example
<docImprint>Oxford, Clarendon Press, 1987</docImprint>
Imprints may be somewhat more complex:
<docImprint>  <pubPlace>London</pubPlace> Printed for <name>E. Nutt</name>, at <pubPlace>Royal Exchange</pubPlace>; <name>J. Roberts</name> in <pubPlace>wick-Lane</pubPlace>; <name>A. Dodd</name> without <pubPlace>Temple-Bar</pubPlace>; and <name>J. Graves</name> in <pubPlace>St. James's-street.</pubPlace>  <date>1722.</date> </docImprint>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="pubPlace"/>
  <elementRef key="docDate"/>
  <elementRef key="publisher"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element docImprint
{
   tei_att.global.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_pubPlace
    | tei_docDate
    | tei_publisher
    | tei_model.global
   )*
}

1.92. <docTitle>

<docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: back front titlePage
May contain
Example
<docTitle>  <titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart>  <titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart> </docTitle>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="titlePart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element docTitle
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   ( tei_model.global*, ( ( tei_titlePart, tei_model.global* )+ ) )
}

1.93. <edition>

<edition> (edition) describes the particularities of one edition of a text. [2.2.2. The Edition Statement]
Moduleheader
Attributes
Member of
Contained by
core: bibl monogr
header: editionStmt
May contain
Example
<edition>First edition <date>Oct 1990</date> </edition> <edition n="S2">Students' edition</edition>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element edition { tei_att.global.attributes, tei_macro.phraseSeq }

1.94. <editionStmt>

<editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Example
<editionStmt>  <edition n="S2">Students' edition</edition>  <respStmt>   <resp>Adapted by </resp>   <name>Elizabeth Kirk</name>  </respStmt> </editionStmt>
Example
<editionStmt>  <p>First edition, <date>Michaelmas Term, 1991.</date>  </p> </editionStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="edition"/>
   <classRef key="model.respLike"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element editionStmt
{
   tei_att.global.attributes,
   ( tei_model.pLike+ | ( tei_edition, tei_model.respLike* ) )
}

1.95. <editor>

<editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

Example
<editor role="Technical_Editor">Ron Van den Branden</editor> <editor role="Editor-in-Chief">John Walsh</editor> <editor role="Managing_Editor">Anne Baillot</editor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element editor
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.96. <editorialDecl>

<editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
Example
<editorialDecl>  <normalization>   <p>All words converted to Modern American spelling using      Websters 9th Collegiate dictionary   </p>  </normalization>  <quotation marks="all">   <p>All opening quotation marks converted to “ all closing      quotation marks converted to &amp;cdq;.</p>  </quotation> </editorialDecl>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.editorialDeclPart"/>
 </alternate>
</content>
    
Schema Declaration
element editorialDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_model.pLike | tei_model.editorialDeclPart )+
}

1.97. <education>

<education> (education) contains a description of the educational experience of a person. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
primary
secondary
undergraduate
graduate
residency
apprenticeship
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<education>Left school at age 16</education>
Example
<education from="1986-01-01"  to="1990-06-30">Attended <name>Cherwell School</name> </education>
Example
<education notBefore="1685-07"  notAfter="1690-06">Anthony Hammond smuggled her into the University of Cambridge, where she was disguised as his male cousin, Jack. She remained there for some months learning grammar, logic, rhetoric, and ethics</education>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element education
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.98. <eg>

<eg> (example) contains any kind of illustrative example. [23.5. Element Specifications 23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
Member of
Contained by
May contain
Note

If the example contains material in XML markup, either it must be enclosed within a CDATA marked section, or character entity references must be used to represent the markup delimiters. If the example contains well-formed XML, it should be marked using the more specific <egXML> element.

Example
<p>The <gi>term</gi> element is declared using the following syntax: <eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg> </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element eg { tei_att.global.attributes, tei_macro.phraseSeq }

1.99. <egXML>

<egXML> (example of XML) a single XML fragment demonstrating the use of some XML, such as elements, attributes, or processing instructions, etc., in which the <egXML> element functions as the root element. [23.1.1. Phrase Level Terms]
Namespacehttp://www.tei-c.org/ns/Examples
Moduletagdocs
Attributes
validindicates the intended validity of the example with respect to a schema.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
true
the example is intended to be fully valid, assuming that its root element, or a provided root element, could have been used as a possible root element in the schema concerned.[Default]
feasible
the example could be transformed into a valid document by inserting any number of valid attributes and child elements anywhere within it; or it is valid against a version of the schema concerned in which the provision of character data, list, element, or attribute values has been made optional.
false
the example is not intended to be valid, and contains deliberate errors.
Member of
Contained by
May containANY
Note

In the source of the TEI Guidelines, this element declares itself and its content as belonging to the namespace http://www.tei-c.org/ns/Examples. This enables the content of the element to be validated independently against the TEI scheme. Where this element is used outside this context, a different namespace or none at all may be preferable. The content must however be a well-formed XML fragment or document: where this is not the case, the more general <eg> element should be used in preference.

Example
<egXML xmlns="http://www.tei-c.org/ns/Examples"><div>   <head>A slide about <gi>egXML</gi>   </head>   <list>    <item>     <gi>egXML</gi> can be used to give XML examples in the TEI        Examples namespace</item>    <item>Attributes values for <att>valid</att>:    <list rend="collapsed">      <item>       <val rend="green">true</val>: intended to be fully            valid</item>      <item>       <val rend="amber">feasible</val>: valid if missing nodes            provided</item>      <item>       <val rend="red">false</val>: not intended to be valid</item>     </list>    </item>    <item>The <att>rend</att> attribute can be        used for recording how parts of the example were rendered.</item>   </list> </div> </egXML>
Example
<egXML valid="feasiblesource="#UND" xmlns="http://www.tei-c.org/ns/Examples"><text>   <front> <!-- front matter for the whole group -->   </front>   <group>    <text> <!-- first text -->    </text>    <text> <!-- second text -->    </text>   </group> </text> <!-- This example is not valid TEI, but could be made so by adding missing components --> </egXML>
Example
      <egXML xmlns="http://www.tei-c.org/ns/Examples" valid="false">          <para xml:lang="en">Doubloons are a pirate's best friend</para>       </egXML>     
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <anyElement/>
 </alternate>
</content>
    
Schema Declaration
element egXML
{
   tei_att.global.attributes,
   attribute valid { "true" | "feasible" | "false" }?,
   ( text | anyElement_egXML_2 )*
}

1.100. <elementRef>

<elementRef> points to the specification for some element which is to be included in a schema [23.2. Modules and Schemas]
Moduletagdocs
Attributes
keythe identifier used for the required element within the source indicated.
StatusRequired
Datatypeteidata.xmlName
Member of
Contained by
May containEmpty element
Note

Elements are identified by the name supplied as value for the ident attribute on the <elementSpec> element in which they are declared. TEI element names are unique.

Example
<elementRef key="p"/>
Include in the schema an element named <p> available from the current default source.
Example
<elementRef key="psource="tei:1.2.1"/>
Include in the schema an element named <p> available from the TEI P5 1.2.1 release.
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element elementRef
{
   tei_att.global.attributes,
   tei_att.repeatable.attributes,
   attribute key { text },
   empty
}

1.101. <elementSpec>

<elementSpec> (element specification) documents the structure, content, and purpose of a single element type. [23.5. Element Specifications 23. Documentation Elements]
Moduletagdocs
Attributes
prefixspecifies a default prefix which will be prepended to all patterns relating to the element, unless otherwise stated.
StatusOptional
Datatype0–1 occurrences of teidata.xmlName separated by whitespace
Member of
Contained by
May contain
Example
<elementSpec module="tagdocsident="code">  <gloss/>  <desc>contains literal code</desc>  <classes>   <memberOf key="model.emphLike"/>  </classes>  <content>   <textNode/>  </content>  <attList>   <attDef ident="typeusage="opt">    <desc>the language of the code</desc>    <datatype>     <dataRef key="teidata.enumerated"/>    </datatype>   </attDef>  </attList> </elementSpec>
Schematron
<sch:rule context="tei:elementSpec[ @mode eq 'delete' ]"> <sch:report test="child::*">This elementSpec element has a mode= of "delete" even though it has child elements. Change the mode= to "add", "change", or "replace", or remove the child elements.</sch:report> </sch:rule> <sch:rule context="tei:elementSpec[ @mode = ('add','change','replace') ]"> <sch:assert test="child::* | (@* except (@mode, @ident))">This elementSpec element has a mode= of "<sch:value-of select="@mode"/>", but does not have any child elements or schema-changing attributes. Specify child elements, use validUntil=, predeclare=, ns=, or prefix=, or change the mode= to "delete".</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="classes" minOccurs="0"/>
  <elementRef key="content" minOccurs="0"/>
  <elementRef key="valList" minOccurs="0"/>
  <elementRef key="constraintSpec"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="attList" minOccurs="0"/>
  <alternate maxOccurs="unbounded"
   minOccurs="0">
   <elementRef key="model"/>
   <elementRef key="modelGrp"/>
   <elementRef key="modelSequence"/>
  </alternate>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="listRef" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element elementSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.namespaceable.attributes,
   attribute prefix { ? }?,
   (
      ( tei_model.identSynonyms | tei_model.descLike )*,
      tei_classes?,
      tei_content?,
      tei_valList?,
      tei_constraintSpec*,
      tei_attList?,
      ( tei_model | tei_modelGrp | tei_modelSequence )*,
      tei_exemplum*,
      tei_remarks*,
      tei_listRef*
   )
}

1.102. <ellipsis>

<ellipsis> (deliberately marked omission) indicates a purposeful marking in the source document signalling that content has been omitted, and may also supply or describe the omitted content. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
Note

Unlike <gap>, which indicates content that the encoder cannot or chooses not to represent, <ellipsis> indicates a passage explicitly signalled in the source document as absent. The <ellipsis> element is not appropriate for every use of ellipsis points, such as when they indicate that a speaker is pausing.

Example
<lg>  <l>What projects men make—what queer turns they take,</l>  <l>Since <emph>steam</emph> has improved our condition;</l>  <l>They never are still, but must cure or must kill</l>  <l>With steam physic or steam ammunition.</l>  <l>But a short time ago, to a quack you would go,</l>  <l>To steam a fat man to a thinner;</l>  <l>Now changed from all that, if you wish to get <emph>fat</emph>,</l>  <l>Come to Barton’s and eat a <emph>steam dinner!</emph>  </l>  <l>Oh dear! think of a scheme, odd though it seem—</l>  <l>I’m sure ’twill succeed if you make it by steam.</l> </lg> <lg>  <l>You may sleep, you may dream, you may travel by steam,</l>  <l>For the outcry is still to go faster;</l>  <l>And what does it reck, should you e’en break your neck,</l>  <l>If ’tis <emph>steam</emph> that brings on the disaster?</l>  <ellipsis resp="#ChambersEdnbrghJrnl1880">   <metamark function="multilineEllipsis"> * * * * </metamark>   <desc resp="#teiProjectEditor2021">The printer omits four lines here,      skipping the second half of the second octave, before the refrain.</desc>  </ellipsis>  <l>Oh dear! think of a scheme, odd though it seem—</l>  <l>I’m sure ’twill succeed if you make it by steam.</l> </lg>
Example
<lg>  <l>You think you’ve lost your love </l>  <l>Well, I saw her yesterday </l>  <l>It’s you she's thinking of </l>  <l>And she told me what to say</l> </lg> <lg xml:id="chorus">  <label>[Refrain]</label>  <l>She says she loves you </l>  <l>And you know that can’t be bad </l>  <l>Yes, she loves you </l>  <l>And you know you should be glad</l> </lg> <lg>  <l>She said you hurt her so </l>  <l>She almost lost her mind </l>  <l>But now she said she knows </l>  <l>You’re not the hurting kind</l> </lg> <ellipsis>  <metamark>******</metamark>  <supplied copyOf="#chorus"/> </ellipsis>
Content model
<content>
 <sequence>
  <elementRef key="metamark"/>
  <classRef key="model.descLike"
   minOccurs="0" maxOccurs="1"/>
  <elementRef key="supplied" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element ellipsis
{
   tei_att.global.attributes,
   tei_att.dimensions.attributes,
   tei_att.timed.attributes,
   ( metamark, tei_model.descLike?, supplied? )
}

1.103. <email>

<email> (electronic mail address) contains an email address identifying a location to which email messages can be delivered. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The format of a modern Internet email address is defined in RFC 2822

Example
<email>membership@tei-c.org</email>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element email
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.104. <emph>

<emph> (emphasized) marks words or phrases which are stressed or emphasized for linguistic or rhetorical effect. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
Contained by
May contain
Example
You took the car and did <emph>what</emph>?!!
Example
<q>What it all comes to is this,</q> he said. <q>  <emph>What    does Christopher Robin do in the morning nowadays?</emph> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element emph
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.105. <empty>

<empty> indicates the presence of an empty node within a content model [23. Documentation Elements]
Moduletagdocs
Attributes
Member of
Contained by
May containEmpty element
Example
<content>  <alternate minOccurs="0"   maxOccurs="unbounded">   <empty/>   <elementRef key="hi"/>  </alternate> </content>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element empty { tei_att.global.attributes, empty }

1.106. <encodingDesc>

<encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Member of
Contained by
header: teiHeader
May contain
Example
<encodingDesc>  <p>Basic encoding, capturing lexical information only. All    hyphenation, punctuation, and variant spellings normalized. No    formatting or layout information preserved.</p> </encodingDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.encodingDescPart"/>
  <classRef key="model.pLike"/>
 </alternate>
</content>
    
Schema Declaration
element encodingDesc
{
   tei_att.global.attributes,
   ( tei_model.encodingDescPart | tei_model.pLike )+
}

1.107. <epigraph>

<epigraph> (epigraph) contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<epigraph xml:lang="la">  <cit>   <bibl>Lucret.</bibl>   <quote>    <l part="F">petere inde coronam,</l>    <l>Vnde prius nulli velarint tempora Musae.</l>   </quote>  </cit> </epigraph>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.common"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element epigraph
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   ( tei_model.common | tei_model.global )*
}

1.108. <equiv>

<equiv> (equivalent) specifies a component which is considered equivalent to the parent element, either by co-reference, or by external link. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Moduletagdocs
Attributes
namea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), naming the underlying concept of which the parent is a representation.
StatusOptional
Datatypeteidata.name
uri(uniform resource identifier) references the underlying concept of which the parent is a representation by means of some external identifier
StatusOptional
Datatypeteidata.pointer
filterreferences an external script which contains a method to transform instances of this element to canonical TEI
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May containEmpty element
Note

The mimeType attribute should be used to supply the MIME media type of the filter script specified by the filter attribute.

ExampleThe following example declares that the <bo> element is conceptually equivalent to the markup construct <hi rend='bold'>, and that an external definition of this concept is available from the URI indicated
<elementSpec ident="himode="change">  <equiv name="BOLD"/>  <desc>bold typography</desc>  <attList>   <attDef ident="rendmode="change">    <valList>     <valItem ident="bold"/>    </valList>   </attDef>  </attList> </elementSpec> <elementSpec ident="bomode="add">  <equiv name="BOLD"   uri="http://www.example.com/typesetting/bold"/> </elementSpec>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element equiv
{
   tei_att.global.attributes,
   tei_att.internetMedia.attributes,
   tei_att.predicate.attributes,
   attribute name { text }?,
   attribute uri { text }?,
   attribute filter { text }?,
   empty
}

1.109. <event>

<event> (event) contains data relating to anything of significance that happens in time. [14.3.1. Basic Principles]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<listEvent>  <event when="1618-05-23"   xml:id="SecondDefPraguewhere="#Prague">   <eventName>1618 Defenestration of Prague</eventName>   <idno>https://www.wikidata.org/wiki/Q13365740</idno>   <listPerson type="defenstrated">    <person>     <persName>Jaroslav Bořita z Martinic</persName>     <idno type="GND">https://d-nb.info/gnd/116810998</idno>    </person>    <person>     <persName>Vilém Slavata z Chlumu a Košumberka</persName>     <idno type="GND">https://d-nb.info/gnd/1018376615</idno>    </person>    <person>     <persName>Filip Fabricius</persName>     <idno type="GND">https://d-nb.info/gnd/133946118</idno>    </person>   </listPerson>   <place xml:id="Prague">    <placeName>Prague</placeName>   </place>  </event>  <event from="1618to="1648"   xml:id="ThirtyYearsWar">   <eventName>Thirty Years’ War</eventName>   <idno>https://www.wikidata.org/wiki/Q2487</idno>   <event when="1643-03-19"    xml:id="BattleofRocroiwhere="#Rocroi">    <eventName>Battle of Rocroi</eventName>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q728480</idno>    <idno type="GND">https://d-nb.info/gnd/4202901-6</idno>    <place xml:id="Rocroi">     <placeName>Rocroi</placeName>     <location>      <geo decls="#WGS">49.926111 4.522222</geo>     </location>    </place>   </event>  </event> </listEvent>
Example
<person>  <event type="matwhen="1972-10-12">   <label>matriculation</label>  </event>  <event type="gradwhen="1975-06-23">   <label>graduation</label>  </event> </person>
Content model
<content>
 <sequence>
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <elementRef key="eventName"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.eventLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPerson"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="listPlace"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <classRef key="model.objectLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element event
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.locatable.attributes,
   tei_att.naming.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   (
      tei_idno*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ | tei_eventName+ ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | linkGrp
       | link
       | tei_idno
       | tei_ptr
      )*,
      tei_model.eventLike*,
      ( tei_model.personLike | tei_listPerson )*,
      ( tei_model.placeLike | tei_listPlace )*,
      tei_model.objectLike*,
      ( tei_relation | tei_listRelation )*
   )
}

1.110. <eventName>

<eventName> (name of an event) contains a proper noun or noun phrase used to refer to an event. [14.2.4. Event Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <event from="1939-09-01to="1945-09-02">   <eventName xml:lang="de">Zweiter Weltkrieg</eventName>   <eventName xml:lang="en">World War II</eventName>   <idno type="GND">https://d-nb.info/gnd/4079167-1</idno>   <idno type="Wikidata">https://www.wikidata.org/wiki/Q362</idno>   <event from="1939-09-01to="1939-10-06"    xml:id="UeberfallAufPolen">    <eventName xml:lang="de">Überfall auf Polen</eventName>    <eventName xml:lang="en">Invasion of Poland</eventName>    <idno type="GND">https://d-nb.info/gnd/4175002-0</idno>    <idno type="LOC">https://id.loc.gov/authorities/sh85148341</idno>    <listPlace type="affected">     <place>      <placeName xml:lang="pl">Gdańsk</placeName>      <location>       <geo>54.350556 18.652778</geo>      </location>     </place>    </listPlace>   </event>   <event from="1941-06-22to="1945-05-09">    <eventName xml:lang="de">Deutsch-Sowjetischer Krieg</eventName>    <eventName xml:lang="ru">Великая Отечественная война</eventName>    <idno type="GND">https://d-nb.info/gnd/4076906-9</idno>    <idno type="Wikidata">https://www.wikidata.org/wiki/Q189266</idno>   </event>  </event> </listEvent>
Example
<p>On <date when="1719-03-19">Monday</date>, <rs type="person">she</rs> was writing about the <eventName ref="#SecondDefPrague">1618 Defenestration of Prague</eventName> which initiated the <rs type="eventref="#ThirtyYearsWar">long war</rs>.</p>
Example
<event from="2019-09-16to="2019-09-20"  xml:id="tei2019graz">  <eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>  <eventName type="short">TEI 2019</eventName>  <note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.    Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the  <ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.  </note>  <listPerson type="LocalOrganizers">   <person>    <persName>     <surname>Raunig</surname>     <forename>Elisabeth</forename>    </persName>   </person>   <person>    <persName>     <surname>Scholger</surname>     <forename>Martina</forename>    </persName>   </person>   <person>    <persName>     <surname>Scholger</surname>     <forename>Walter</forename>    </persName>   </person>   <person>    <persName>     <surname>Steiner</surname>     <forename>Elisabeth</forename>    </persName>   </person>   <person>    <persName>     <surname>Vogeler</surname>     <forename>Georg</forename>    </persName>   </person>  </listPerson>  <place xml:lang="de">   <placeName>Universität Graz</placeName>   <location>    <address>     <addrLine>ReSoWi Gebäude</addrLine>     <addrLine>Universitätsstraße 15</addrLine>     <postCode>8010</postCode>     <settlement>Graz</settlement>     <country>Österreich</country>    </address>    <geo>15.451651587656 47.078215112534</geo>   </location>  </place>  <listRelation>   <relation active="#tei2019graz"    passive="#AnnualTEIConferencetype="CRMname="P31_is_instance_of"    ref="https://www.wikidata.org/wiki/Property:P31"/>  </listRelation> </event>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element eventName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

1.111. <exemplum>

<exemplum> (exemplum) groups an example demonstrating the use of an element along with optional paragraphs of commentary. [23.5. Element Specifications]
Moduletagdocs
Attributes
Contained by
May contain
core: p
tagdocs: eg egXML
Example
<exemplum xml:lang="en">  <p>The <gi>name</gi> element can be used for both personal names and place names:</p>  <eg xml:space="preserve"><![CDATA[ <q>My dear <name type="person">Mr.           Bennet</name>,</q> said his lady to him one day,           <q>have you heard that <name type="place">Netherfield           Park</name> is let at last?</q>]]></eg>  <p>As shown above, the <att>type</att> attribute may be used to distinguish the one from the    other.</p> </exemplum>
Content model
<content>
 <sequence>
  <classRef key="model.pLike" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="egXML"/>
   <elementRef key="eg"/>
  </alternate>
  <classRef key="model.pLike" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element exemplum
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.translatable.attributes,
   ( tei_model.pLike*, ( tei_egXML | tei_eg ), tei_model.pLike* )
}

1.112. <expan>

<expan> (expansion) contains the expansion of an abbreviation. [3.6.5. Abbreviations and Their Expansions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The content of this element should be the expanded abbreviation, usually (but not always) a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion.

If abbreviations are expanded silently, this practice should be documented in the <editorialDecl>, either with a <normalization> element or a <p>.

Example
The address is Southmoor <choice>  <expan>Road</expan>  <abbr>Rd</abbr> </choice>
Example
<choice xml:lang="la">  <abbr>Imp</abbr>  <expan>Imp<ex>erator</ex>  </expan> </choice>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element expan
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.113. <extent>

<extent> (extent) describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.7.1. Object Description]
Moduleheader
Attributes
Member of
Contained by
May contain
Example
<extent>3200 sentences</extent> <extent>between 10 and 20 Mb</extent> <extent>ten 3.5 inch high density diskettes</extent>
ExampleThe <measure> element may be used to supply normalized or machine tractable versions of the size or sizes concerned.
<extent>  <measure unit="MiBquantity="4.2">About four megabytes</measure>  <measure unit="pagesquantity="245">245 pages of source    material</measure> </extent>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element extent { tei_att.global.attributes, tei_macro.phraseSeq }

1.114. <faith>

<faith> (faith) specifies the faith, religion, or belief set of a person. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
practicing
clandestine
patrilineal
matrilineal
convert
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<faith>protestant</faith>
Example
<faith ref="http://dbpedia.org/page/Manichaeism">Manichaeism</faith>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element faith
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.canonical.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.115. <fileDesc>

<fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
May contain
Note

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

Example
<fileDesc>  <titleStmt>   <title>The shortest possible TEI document</title>  </titleStmt>  <publicationStmt>   <p>Distributed as part of TEI P5</p>  </publicationStmt>  <sourceDesc>   <p>No print source exists: this is an original digital text</p>  </sourceDesc> </fileDesc>
Content model
<content>
 <sequence>
  <sequence>
   <elementRef key="titleStmt"/>
   <elementRef key="editionStmt"
    minOccurs="0"/>
   <elementRef key="extent" minOccurs="0"/>
   <elementRef key="publicationStmt"/>
   <elementRef key="seriesStmt"
    minOccurs="0" maxOccurs="unbounded"/>
   <elementRef key="notesStmt"
    minOccurs="0"/>
  </sequence>
  <elementRef key="sourceDesc"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element fileDesc
{
   tei_att.global.attributes,
   (
      (
         tei_titleStmt,
         tei_editionStmt?,
         tei_extent?,
         tei_publicationStmt,
         tei_seriesStmt*,
         tei_notesStmt?
      ),
      tei_sourceDesc+
   )
}

1.116. <floatingText>

<floatingText> (floating text) contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Note

A floating text has the same content as any other <text> and may thus be interrupted by another floating text, or contain a <group> of tesselated texts.

Example
<body>  <div type="scene">   <sp>    <p>Hush, the players begin...</p>   </sp>   <floatingText type="pwp">    <body>     <div type="act">      <sp>       <l>In Athens our tale takes place [...]</l>      </sp> <!-- ... rest of nested act here -->     </div>    </body>   </floatingText>   <sp>    <p>Now that the play is finished ...</p>   </sp>  </div> </body>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element floatingText
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.global*,
      ( ( tei_front, tei_model.global* )? ),
      ( tei_body | tei_group ),
      tei_model.global*,
      ( ( tei_back, tei_model.global* )? )
   )
}

1.117. <floruit>

<floruit> (floruit) contains information about a person's period of activity. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<floruit notBefore="1066notAfter="1100"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element floruit
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.dimensions.attributes,
   tei_att.editLike.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.118. <foreign>

<foreign> (foreign) identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.

This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element.

The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages.

Example
This is heathen Greek to you still? Your <foreign xml:lang="la">lapis philosophicus</foreign>?
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element foreign
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.119. <forename>

<forename> (forename) contains a forename, given or baptismal name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <roleName>Ex-President</roleName>  <forename>George</forename>  <surname>Bush</surname> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element forename
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.120. <front>

<front> (front matter) contains any prefatory matter (headers, abstracts, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText text
May contain
Note

Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical.

Example
<front>  <epigraph>   <quote>Nam Sibyllam quidem Cumis ego ipse oculis meis vidi in ampulla      pendere, et cum illi pueri dicerent: <q xml:lang="grc">Σίβυλλα τί        θέλεις</q>; respondebat illa: <q xml:lang="grc">ὰποθανεῖν θέλω.</q>   </quote>  </epigraph>  <div type="dedication">   <p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>   </p>  </div> </front>
Example
<front>  <div type="dedication">   <p>To our three selves</p>  </div>  <div type="preface">   <head>Author's Note</head>   <p>All the characters in this book are purely imaginary, and if the      author has used names that may suggest a reference to living persons      she has done so inadvertently. ...</p>  </div> </front>
Example
<front>  <div type="abstract">   <div>    <head> BACKGROUND:</head>    <p>Food insecurity can put children at greater risk of obesity because        of altered food choices and nonuniform consumption patterns.</p>   </div>   <div>    <head> OBJECTIVE:</head>    <p>We examined the association between obesity and both child-level        food insecurity and personal food insecurity in US children.</p>   </div>   <div>    <head> DESIGN:</head>    <p>Data from 9,701 participants in the National Health and Nutrition        Examination Survey, 2001-2010, aged 2 to 11 years were analyzed.        Child-level food insecurity was assessed with the US Department of        Agriculture's Food Security Survey Module based on eight        child-specific questions. Personal food insecurity was assessed with        five additional questions. Obesity was defined, using physical        measurements, as body mass index (calculated as kg/m2) greater than        or equal to the age- and sex-specific 95th percentile of the Centers        for Disease Control and Prevention growth charts. Logistic        regressions adjusted for sex, race/ethnic group, poverty level, and        survey year were conducted to describe associations between obesity        and food insecurity.</p>   </div>   <div>    <head> RESULTS:</head>    <p>Obesity was significantly associated with personal food insecurity        for children aged 6 to 11 years (odds ratio=1.81; 95% CI 1.33 to        2.48), but not in children aged 2 to 5 years (odds ratio=0.88; 95%        CI 0.51 to 1.51). Child-level food insecurity was not associated        with obesity among 2- to 5-year-olds or 6- to 11-year-olds.</p>   </div>   <div>    <head> CONCLUSIONS:</head>    <p>Personal food insecurity is associated with an increased risk of        obesity only in children aged 6 to 11 years. Personal        food-insecurity measures may give different results than aggregate        food-insecurity measures in children.</p>   </div>  </div> </front>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.frontPart"/>
   <classRef key="model.pLike"/>
   <classRef key="model.pLike.front"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence minOccurs="0">
   <alternate>
    <sequence>
     <classRef key="model.div1Like"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.div1Like"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
    <sequence>
     <classRef key="model.divLike"/>
     <alternate minOccurs="0"
      maxOccurs="unbounded">
      <classRef key="model.divLike"/>
      <classRef key="model.frontPart"/>
      <classRef key="model.global"/>
     </alternate>
    </sequence>
   </alternate>
   <sequence minOccurs="0">
    <classRef key="model.divBottom"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.divBottom"/>
     <classRef key="model.global"/>
    </alternate>
   </sequence>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element front
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   (
      (
         tei_model.frontPart
       | tei_model.pLike
       | tei_model.pLike.front
       | tei_model.global
      )*,
      (
         (
            (
               (
                  tei_model.div1Like,
                  (
                     tei_model.div1Like
                   | tei_model.frontPart
                   | tei_model.global
                  )*
               )
             | (
                  tei_model.divLike,
                  (
                     tei_model.divLike
                   | tei_model.frontPart
                   | tei_model.global
                  )*
               )
            ),
            (
               (
                  tei_model.divBottom,
                  ( tei_model.divBottom | tei_model.global )*
               )?
            )
         )?
      )
   )
}

1.121. <funder>

<funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Funders provide financial support for a project; they are distinct from sponsors (see element <sponsor>), who provide intellectual support and authority.

Example
<funder>The National Endowment for the Humanities, an independent federal agency</funder> <funder>Directorate General XIII of the Commission of the European Communities</funder> <funder>The Andrew W. Mellon Foundation</funder> <funder>The Social Sciences and Humanities Research Council of Canada</funder>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element funder
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.122. <gap>

<gap> (gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
reason(reason) gives the reason for omission
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
cancelled
(cancelled)
deleted
(deleted)
editorial
(editorial) for features omitted from transcription due to editorial policy
illegible
(illegible)
inaudible
(inaudible)
irrelevant
(irrelevant)
sampling
(sampling)
agent(agent) in the case of text omitted because of damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
(rubbing) damage results from rubbing of the leaf edges
mildew
(mildew) damage results from mildew on the leaf surface
smoke
(smoke) damage results from smoke
Member of
Contained by
May contain
core: desc
Note

The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion.

Example
<gap quantity="4unit="chars"  reason="illegible"/>
Example
<gap quantity="1unit="essay"  reason="sampling"/>
Example
<del>  <gap atLeast="4atMost="8unit="chars"   reason="illegible"/> </del>
Example
<gap extent="several linesreason="lost"/>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.descLike"/>
  <classRef key="model.certLike"/>
 </alternate>
</content>
    
Schema Declaration
element gap
{
   tei_att.global.attributes,
   tei_att.timed.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute reason
   {
      list
      {
         (
            "cancelled"
          | "deleted"
          | "editorial"
          | "illegible"
          | "inaudible"
          | "irrelevant"
          | "sampling"
         )+
      }
   }?,
   attribute agent { text }?,
   ( tei_model.descLike | tei_model.certLike )*
}

1.123. <gb>

<gb> (gathering beginning) marks the beginning of a new gathering or quire in a transcribed codex. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <gb> elements should appear at the start of the first page in the gathering. The global n attribute indicates the number or other value used to identify this gathering in a collation.

The type attribute may be used to further characterize the gathering in any respect.

Example
<gb n="iii"/> <pb n="2r"/> <!-- material from page 2 recto of gathering iii here --> <pb n="2v"/> <!-- material from page 2 verso of gathering iii here -->
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element gb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.spanning.attributes,
   tei_att.breaking.attributes,
   tei_att.edition.attributes,
   tei_att.cmc.attributes,
   empty
}

1.124. <genName>

<genName> (generational name component) contains a name component used to distinguish otherwise similar names on the basis of the relative ages or generations of the persons named. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<persName>  <forename>Charles</forename>  <genName>II</genName> </persName>
Example
<persName>  <surname>Pitt</surname>  <genName>the Younger</genName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element genName
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.125. <gender>

<gender> (gender) specifies the gender identity of a person, persona, or character. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
valuesupplies a coded value for gender identity
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
May contain
Note

As with other culturally-constructed traits such as age and sex, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<gender value="W">woman</gender>
Example
<gender value="NB">non-binary</gender>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gender
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   tei_macro.phraseSeq
}

1.126. <geo>

<geo> (geographical coordinates) contains any expression of a set of geographic coordinates, representing a point, line, or area on the surface of the earth in some notation. [14.3.4.1. Varieties of Location]
Modulenamesdates
Attributes
Member of
Contained by
May containCharacter data only
Note

Uses of <geo> can be associated with a coordinate system, defined by a <geoDecl> element supplied in the TEI header, using the decls attribute. If no such link is made, the assumption is that the content of each <geo> element will be a pair of numbers separated by whitespace, to be interpreted as latitude followed by longitude according to the World Geodetic System.

Example
<geoDecl xml:id="WGSdatum="WGS84">World Geodetic System</geoDecl> <geoDecl xml:id="OSdatum="OSGB36">Ordnance Survey</geoDecl> <!-- ... --> <location>  <desc>A tombstone plus six lines of    Anglo-Saxon text, built into the west tower (on the south side    of the archway, at 8 ft. above the ground) of the    Church of St. Mary-le-Wigford in Lincoln.</desc>  <geo decls="#WGS">53.226658 -0.541254</geo>  <geo decls="#OS">SK 97481 70947</geo> </location>
Example
<geo>41.687142 -74.870109</geo>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element geo
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.cmc.attributes,
   text
}

1.127. <geoDecl>

<geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <geo> element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration]
Moduleheader
Attributes
datumsupplies a commonly used code name for the datum employed.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
WGS84
(World Geodetic System) a pair of numbers to be interpreted as latitude followed by longitude according to the World Geodetic System.[Default]
MGRS
(Military Grid Reference System) the values supplied are geospatial entity object codes, based on
OSGB36
(ordnance survey great britain) the value supplied is to be interpreted as a British National Grid Reference.
ED50
(European Datum coordinate system) the value supplied is to be interpreted as latitude followed by longitude according to the European Datum coordinate system.
Member of
Contained by
header: encodingDesc
May contain
Example
<geoDecl datum="OSGB36"/>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geoDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute datum { "WGS84" | "MGRS" | "OSGB36" | "ED50" }?,
   tei_macro.phraseSeq
}

1.128. <geogFeat>

<geogFeat> (geographical feature name) contains a common noun identifying some geographical feature contained within a geographic name, such as valley, mount, etc. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<geogName> The <geogFeat>vale</geogFeat> of White Horse</geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geogFeat
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.129. <geogName>

<geogName> (geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<geogName>  <geogFeat>Mount</geogFeat>  <name>Sinai</name> </geogName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element geogName
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.130. <gi>

<gi> (element name) contains the name (generic identifier) of an element. [23. Documentation Elements 23.5. Element Specifications]
Moduletagdocs
Attributes
schemesupplies the name of the scheme in which this name is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
this element is part of the TEI scheme.[Default]
DBK
(docbook) this element is part of the Docbook scheme.
XX
(unknown) this element is part of an unknown scheme.
Schematron
this element is from Schematron.
HTML
this element is from the HTML scheme.
Member of
Contained by
May contain
XSD Name
Example
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the <gi scheme="DBK">listItem</gi> element.</p>
This example shows the use of both a namespace prefix and the scheme attribute as alternative ways of indicating that the <gi> in question is not a TEI element name: in practice only one method should be adopted.
Content model
<content>
 <dataRef key="teidata.name"/>
</content>
    
Schema Declaration
element gi
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   teidata.name
}

1.131. <gloss>

<gloss> (gloss) identifies a phrase or word used to provide a gloss or definition for some other word or phrase. [3.4.1. Terms and Glosses 23.4.1. Description of Components]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
We may define <term xml:id="tdpvrend="sc">discoursal point of view</term> as <gloss target="#tdpv">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element gloss
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.translatable.attributes,
   tei_att.typed.attributes,
   tei_att.pointing.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.132. <graphic>

<graphic> (graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it. [3.10. Graphics and Other Non-textual Components 12.1. Digital Facsimiles]
Modulecore
Attributes
Member of
Contained by
May contain
core: desc
Note

The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute.

Within the body of a text, a <graphic> element indicates the presence of a graphic component in the source itself. Within the context of a <facsimile> or <sourceDoc> element, however, a <graphic> element provides an additional digital representation of some part of the source being encoded.

Example
<figure>  <graphic url="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<facsimile>  <surfaceGrp n="leaf1">   <surface>    <graphic url="page1.png"/>   </surface>   <surface>    <graphic url="page2-highRes.png"/>    <graphic url="page2-lowRes.png"/>   </surface>  </surfaceGrp> </facsimile>
Example
<facsimile>  <surfaceGrp n="leaf1xml:id="spi001">   <surface xml:id="spi001r">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001r.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001r.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001r.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001r.jpg"/>   </surface>   <surface xml:id="spi001v">    <graphic type="normal"     subtype="thumbnailurl="spi/thumb/001v.jpg"/>    <graphic type="normalsubtype="low-res"     url="spi/normal/lowRes/001v.jpg"/>    <graphic type="normal"     subtype="high-resurl="spi/normal/highRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="low-resurl="spi/contrast/lowRes/001v.jpg"/>    <graphic type="high-contrast"     subtype="high-resurl="spi/contrast/highRes/001v.jpg"/>    <zone xml:id="spi001v_detail01">     <graphic type="normal"      subtype="thumbnailurl="spi/thumb/001v-detail01.jpg"/>     <graphic type="normal"      subtype="low-res"      url="spi/normal/lowRes/001v-detail01.jpg"/>     <graphic type="normal"      subtype="high-res"      url="spi/normal/highRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="low-res"      url="spi/contrast/lowRes/001v-detail01.jpg"/>     <graphic type="high-contrast"      subtype="high-res"      url="spi/contrast/highRes/001v-detail01.jpg"/>    </zone>   </surface>  </surfaceGrp> </facsimile>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element graphic
{
   tei_att.global.attributes,
   tei_att.media.attributes,
   tei_att.resourced.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_model.descLike*
}

1.133. <group>

<group> (group) contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Contained by
textstructure: floatingText group text
May contain
Example
<text> <!-- Section on Alexander Pope starts -->  <front> <!-- biographical notice by editor -->  </front>  <group>   <text> <!-- first poem -->   </text>   <text> <!-- second poem -->   </text>  </group> </text> <!-- end of Pope section-->
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <sequence>
   <alternate>
    <elementRef key="text"/>
    <elementRef key="group"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="text"/>
    <elementRef key="group"/>
    <classRef key="model.global"/>
   </alternate>
  </sequence>
  <classRef key="model.divBottom"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element group
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         ( tei_text | tei_group ),
         ( tei_text | tei_group | tei_model.global )*
      ),
      tei_model.divBottom*
   )
}

1.134. <handNote>

<handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
May contain
Example
<handNote scope="sole">  <p>Written in insular    phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed    minuscule.</p> </handNote>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element handNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

1.135. <head>

<head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section.

ExampleThe most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example:
<div1 n="Itype="book">  <head>In the name of Christ here begins the first book of the ecclesiastical history of    Georgius Florentinus, known as Gregory, Bishop of Tours.</head>  <div2 type="section">   <head>In the name of Christ here begins Book I of the history.</head>   <p>Proposing as I do ...</p>   <p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve      years passed.</p>   <trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six      years from the beginning of the world down to the death of Saint Martin.</trailer>  </div2> </div1>
ExampleWhen headings are not inline with the running text (see e.g. the heading "Secunda conclusio") they might however be encoded as if. The actual placement in the source document can be captured with the place attribute.
<div type="subsection">  <head place="margin">Secunda conclusio</head>  <p>   <lb n="1251"/>   <hi rend="large">Potencia: habitus: et actus: recipiunt speciem ab obiectis<supplied>.</supplied>   </hi>   <lb n="1252"/>Probatur sic. Omne importans necessariam habitudinem ad proprium    [...]  </p> </div>
ExampleThe <head> element is also used to mark headings of other units, such as lists:
With a few exceptions, connectives are equally useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">  <head>Connectives</head>  <item>above</item>  <item>accordingly</item>  <item>across from</item>  <item>adjacent to</item>  <item>again</item>  <item> <!-- ... -->  </item> </list>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element head
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

1.136. <headItem>

<headItem> (heading for list items) contains the heading for the item or gloss column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headItem> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headItem { tei_att.global.attributes, tei_macro.phraseSeq }

1.137. <headLabel>

<headLabel> (heading for list labels) contains the heading for the label or term column in a glossary list or similar structured list. [3.8. Lists]
Modulecore
Attributes
Contained by
core: list
May contain
Note

The <headLabel> element may appear only if each item in the list is preceded by a <label>.

Example
The simple, straightforward statement of an idea is preferable to the use of a worn-out expression. <list type="gloss">  <headLabel rend="smallcaps">TRITE</headLabel>  <headItem rend="smallcaps">SIMPLE, STRAIGHTFORWARD</headItem>  <label>bury the hatchet</label>  <item>stop fighting, make peace</item>  <label>at loose ends</label>  <item>disorganized</item>  <label>on speaking terms</label>  <item>friendly</item>  <label>fair and square</label>  <item>completely honest</item>  <label>at death's door</label>  <item>near death</item> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element headLabel { tei_att.global.attributes, tei_macro.phraseSeq }

1.138. <hi>

<hi> (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made. [3.3.2.2. Emphatic Words and Phrases 3.3.2. Emphasis, Foreign Words, and Unusual Language]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<hi rend="gothic">And this Indenture further witnesseth</hi> that the said <hi rend="italic">Walter Shandy</hi>, merchant, in consideration of the said intended marriage ...
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element hi
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.139. <hyphenation>

<hyphenation> (hyphenation) summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
eol(end-of-line) indicates whether or not end-of-line hyphenation has been retained in a text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
all end-of-line hyphenation has been retained, even though the lineation of the original may not have been.
some
end-of-line hyphenation has been retained in some cases.[Default]
hard
all soft end-of-line hyphenation has been removed: any remaining end-of-line hyphenation should be retained.
none
all end-of-line hyphenation has been removed: any remaining hyphenation occurred within the line.
Member of
Contained by
May contain
core: p
Example
<hyphenation eol="some">  <p>End-of-line hyphenation silently removed where appropriate</p> </hyphenation>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element hyphenation
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute eol { "all" | "some" | "hard" | "none" }?,
   tei_model.pLike+
}

1.140. <ident>

<ident> (identifier) contains an identifier or name for an object of some kind in a formal language. <ident> is used for tokens such as variable names, class names, type names, function names etc. in formal programming languages. [23.1.1. Phrase Level Terms]
Moduletagdocs
Attributes
Member of
Contained by
May containCharacter data only
Note

In running prose, this element may be used for any kind of identifier in any formal language. It should not be used for element and attribute names in XML, for which the special elements <gi> and <att> are provided.

Example
<ident type="ns">http://www.tei-c.org/ns/Examples</ident>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element ident { tei_att.global.attributes, tei_att.typed.attributes, text }

1.141. <idno>

<idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [14.3.1. Basic Principles 2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Moduleheader
Attributes
typecategorizes the identifier, for example as an ISBN, Social Security number, etc.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
ISBN
International Standard Book Number: a 13- or (if assigned prior to 2007) 10-digit identifying number assigned by the publishing industry to a published book or similar item, registered with the International ISBN Agency.
ISSN
International Standard Serial Number: an eight-digit number to uniquely identify a serial publication.
DOI
Digital Object Identifier: a unique string of letters and numbers assigned to an electronic document.
URI
Uniform Resource Identifier: a string of characters to uniquely identify a resource, following the syntax of RFC 3986.
VIAF
A data number in the Virtual Internet Authority File assigned to link different names in catalogs around the world for the same entity.
ESTC
English Short-Title Catalogue number: an identifying number assigned to a document in English printed in the British Isles or North America before 1801.
OCLC
OCLC control number (record number) for the union catalog record in WorldCat, a union catalog for member libraries in the Online Computer Library Center global cooperative.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
header: idno
character data
Note

<idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI.

Example
<idno type="ISBN">978-1-906964-22-1</idno> <idno type="ISSN">0143-3385</idno> <idno type="DOI">10.1000/123</idno> <idno type="URI">http://www.worldcat.org/oclc/185922478</idno> <idno type="URI">http://authority.nzetc.org/463/</idno> <idno type="LT">Thomason Tract E.537(17)</idno> <idno type="Wing">C695</idno> <idno type="oldCat">  <g ref="#sym"/>345 </idno>
In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="idno"/>
 </alternate>
</content>
    
Schema Declaration
element idno
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type
   {
      "ISBN" | "ISSN" | "DOI" | "URI" | "VIAF" | "ESTC" | "OCLC"
   }?,
   attribute calendar { list { + } }?,
   ( text | tei_model.gLike | tei_idno )*
}

1.142. <imprimatur>

<imprimatur> (imprimatur) contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages]
Moduletextstructure
Attributes
Member of
Contained by
textstructure: titlePage
May contain
Example
<imprimatur>Licensed and entred acording to Order.</imprimatur>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element imprimatur { tei_att.global.attributes, tei_macro.paraContent }

1.143. <imprint>

<imprint> groups information relating to the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Contained by
core: monogr
May contain
Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="classCode"/>
   <elementRef key="catRef"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate>
    <classRef key="model.imprintPart"/>
    <classRef key="model.dateLike"/>
   </alternate>
   <elementRef key="respStmt" minOccurs="0"
    maxOccurs="unbounded"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element imprint
{
   tei_att.global.attributes,
   (
      ( tei_classCode | tei_catRef )*,
      (
         (
            ( tei_model.imprintPart | tei_model.dateLike ),
            tei_respStmt*,
            tei_model.global*
         )+
      )
   )
}

1.144. <index>

<index> (index entry) marks a location to be indexed for whatever purpose. [3.9.2. Index Entries]
Modulecore
Attributes
indexNamea single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name), supplying a name to specify which index (of several) the index entry belongs to.
StatusOptional
Datatypeteidata.name
Note

This attribute makes it possible to create multiple indexes for a text.

Member of
Contained by
May contain
core: index term
Example
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term>Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura <index indexName="PLACES">  <term>Sura</term> </index> was David's own first cousin.
Content model
<content>
 <sequence minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="term"/>
  <elementRef key="index" minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element index
{
   tei_att.global.attributes,
   tei_att.spanning.attributes,
   tei_att.cmc.attributes,
   attribute indexName { text }?,
   ( ( tei_term, tei_index? )* )
}

1.145. <interpretation>

<interpretation> (interpretation) describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<interpretation>  <p>The part of speech analysis applied throughout section 4 was added by hand and has not    been checked</p> </interpretation>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element interpretation
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.146. <item>

<item> (item) contains one component of a list. [3.8. Lists 2.6. The Revision Description]
Modulecore
Attributes
Contained by
core: list
May contain
Note

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n.

Example
<list rend="numbered">  <head>Here begin the chapter headings of Book IV</head>  <item n="4.1">The death of Queen Clotild.</item>  <item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>  <item n="4.3">The wives and children of Lothar.</item>  <item n="4.4">The Counts of the Bretons.</item>  <item n="4.5">Saint Gall the Bishop.</item>  <item n="4.6">The priest Cato.</item>  <item> ...</item> </list>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element item
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_macro.specialPara
}

1.147. <keywords>

<keywords> (keywords) contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification]
Moduleheader
Attributes
schemeidentifies the controlled vocabulary within which the set of keywords concerned is defined, for example by a <taxonomy> element, or by some other resource.
StatusOptional
Datatypeteidata.pointer
Contained by
header: textClass
May contain
core: list term
Note

Each individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within an <item> inside a <list> is permitted for backwards compatibility, but is deprecated.

If no control list exists for the keywords used, then no value should be supplied for the scheme attribute.

Example
<keywords scheme="http://classificationweb.net">  <term>Babbage, Charles</term>  <term>Mathematicians - Great Britain - Biography</term> </keywords>
Example
<keywords>  <term>Fermented beverages</term>  <term>Central Andes</term>  <term>Schinus molle</term>  <term>Molle beer</term>  <term>Indigenous peoples</term>  <term>Ethnography</term>  <term>Archaeology</term> </keywords>
Content model
<content>
 <alternate>
  <elementRef key="term" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="list"/>
 </alternate>
</content>
    
Schema Declaration
element keywords
{
   tei_att.global.attributes,
   attribute scheme { text }?,
   ( tei_term+ | tei_list )
}

1.148. <l>

<l> (verse line) contains a single, possibly incomplete, line of verse. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<l met="x/x/x/x/x/real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l>
Schematron
<sch:rule context="tei:l"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]">Abstract model violation: Lines may not contain lines or lg elements.</sch:report> </sch:rule>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element l
{
   tei_att.global.attributes,
   tei_att.fragmentable.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.global
   )*
}

1.149. <label>

<label> (label) contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.8. Lists]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleLabels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:
<list type="glossxml:lang="enm">  <head xml:lang="en">Vocabulary</head>  <headLabel xml:lang="en">Middle English</headLabel>  <headItem xml:lang="en">New English</headItem>  <label>nu</label>  <item xml:lang="en">now</item>  <label>lhude</label>  <item xml:lang="en">loudly</item>  <label>bloweth</label>  <item xml:lang="en">blooms</item>  <label>med</label>  <item xml:lang="en">meadow</item>  <label>wude</label>  <item xml:lang="en">wood</item>  <label>awe</label>  <item xml:lang="en">ewe</item>  <label>lhouth</label>  <item xml:lang="en">lows</item>  <label>sterteth</label>  <item xml:lang="en">bounds, frisks (cf. <cit>    <ref>Chaucer, K.T.644</ref>    <quote>a courser, <term>sterting</term>as the fyr</quote>   </cit>  </item>  <label>verteth</label>  <item xml:lang="la">pedit</item>  <label>murie</label>  <item xml:lang="en">merrily</item>  <label>swik</label>  <item xml:lang="en">cease</item>  <label>naver</label>  <item xml:lang="en">never</item> </list>
ExampleLabels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element:
I will add two facts, which have seldom occurred in the composition of six, or at least of five quartos. <list rend="runontype="ordered">  <label>(1)</label>  <item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>  <label>(2) </label>  <item>Not a sheet has been seen by any human eyes, excepting those of the author and the    printer: the faults and the merits are exclusively my own.</item> </list>
ExampleLabels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:
<list type="gloss">  <label>March 1757.</label>  <item>I wrote some critical observations upon Plautus.</item>  <label>March 8th.</label>  <item>I wrote a long dissertation upon some lines of Virgil.</item>  <label>June.</label>  <item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus      amori.</quote>  </item>  <label>August.</label>  <item>I went to Crassy, and staid two days.</item> </list>
Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.
ExampleLabels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it.
<p>[...] <lb/>&amp; n’entrer en mauuais &amp; mal-heu- <lb/>ré meſnage. Or des que le conſente- <lb/>ment des parties y eſt le mariage eſt <lb/> arreſté, quoy que de faict il ne ſoit <label place="margin">Puiſſance maritale    entre les Romains.</label>  <lb/> conſommé. Depuis la conſomma- <lb/>tion du mariage la femme eſt ſoubs <lb/> la puiſſance du mary, s’il n’eſt eſcla- <lb/>ue ou enfant de famille : car en ce <lb/> cas, la femme, qui a eſpouſé vn en- <lb/>fant de famille, eſt ſous la puiſſance [...]</p>
In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element label
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.150. <langKnowledge>

<langKnowledge> (language knowledge) summarizes the state of a person's linguistic knowledge, either as prose or by a list of <langKnown> elements. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
listening
speaking
reading
writing
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
tagssupplies one or more valid language tags for the languages specified
StatusOptional
Datatype1–∞ occurrences of teidata.language separated by whitespace
Note

This attribute should be supplied only if the element contains no <langKnown> children. Its values are language ‘tags’ as defined in RFC 4646 or its successor

Member of
Contained by
May contain
core: p
namesdates: langKnown
Example
<langKnowledge tags="en-GB fr">  <p>British English and French</p> </langKnowledge>
Example
<langKnowledge>  <langKnown tag="en-GBlevel="H">British English</langKnown>  <langKnown tag="frlevel="M">French</langKnown> </langKnowledge>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"/>
   <elementRef key="langKnown"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element langKnowledge
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute tags { list { + } }?,
   ( precision*, ( tei_model.pLike | tei_langKnown+ ) )
}

1.151. <langKnown>

<langKnown> (language known) summarizes the state of a person's linguistic competence, i.e., knowledge of a single language. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
tagsupplies a valid language tag for the language concerned.
StatusRequired
Datatypeteidata.language
Note

The value for this attribute should be a language ‘tag’ as defined in BCP 47.

levela code indicating the person's level of knowledge for this language
StatusOptional
Datatypeteidata.word
Contained by
namesdates: langKnowledge
May contain
Example
<langKnown tag="en-GBlevel="H">British English</langKnown> <langKnown tag="frlevel="M">French</langKnown>
Example
<person sex="mrole="speaker collaborator"> <!-- other details omitted -->  <langKnowledge>   <langKnown tag="mix">Mixtepec-Mixtec</langKnown>   <langKnown tag="en">English</langKnown>   <langKnown tag="es">Spanish</langKnown>  </langKnowledge> </person>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element langKnown
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   attribute calendar { list { + } }?,
   attribute tag { text },
   attribute level { text }?,
   tei_macro.phraseSeq.limited
}

1.152. <langUsage>

<langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
core: p
header: language
Example
<langUsage>  <language ident="fr-CAusage="60">Québecois</language>  <language ident="en-CAusage="20">Canadian business English</language>  <language ident="en-GBusage="20">British English</language> </langUsage>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="language" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element langUsage
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_model.pLike+ | tei_language+ )
}

1.153. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]
Moduleheader
Attributes
ident(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.
StatusRequired
Datatypeteidata.language
usagespecifies the approximate percentage of the text which uses this language.
StatusOptional
DatatypenonNegativeInteger
Contained by
header: langUsage
May contain
Note

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

Example
<langUsage>  <language ident="en-USusage="75">modern American English</language>  <language ident="az-Arabusage="20">Azerbaijani in Arabic script</language>  <language ident="x-lapusage="05">Pig Latin</language> </langUsage>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element language
{
   tei_att.global.attributes,
   attribute ident { text },
   attribute usage { text }?,
   tei_macro.phraseSeq.limited
}

1.154. <lb>

<lb> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text. [3.11.3. Milestone Elements 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

By convention, <lb> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.

The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives.

ExampleThis example shows typographical line breaks within metrical lines, where they occur at different places in different editions:
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
ExampleThis example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word.
<titlePart>  <lb/>With Additions, ne-<lb break="no"/>ver before Printed. </titlePart>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element lb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   empty
}

1.155. <lg>

<lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.13.1. Core Tags for Verse 3.13. Passages of Verse or Drama 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Note

contains verse lines or nested line groups only, possibly prefixed by a heading.

Example
<lg type="free">  <l>Let me be my own fool</l>  <l>of my own making, the sum of it</l> </lg> <lg type="free">  <l>is equivocal.</l>  <l>One says of the drunken farmer:</l> </lg> <lg type="free">  <l>leave him lay off it. And this is</l>  <l>the explanation.</l> </lg>
Schematron
<sch:rule context="tei:lg"> <sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) > 0">An lg element must contain at least one child l, lg, or gap element.</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:lg"> <sch:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]">Abstract model violation: Lines may not contain line groups.</sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
  </alternate>
  <alternate>
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <elementRef key="lg"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.lLike"/>
   <classRef key="model.stageLike"/>
   <classRef key="model.labelLike"/>
   <classRef key="model.pPart.transcriptional"/>
   <classRef key="model.global"/>
   <elementRef key="lg"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element lg
{
   tei_att.global.attributes,
   tei_att.divLike.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   tei_att.cmc.attributes,
   (
      ( tei_model.divTop | tei_model.global )*,
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_lg
      ),
      (
         tei_model.lLike
       | tei_model.stageLike
       | tei_model.labelLike
       | tei_model.pPart.transcriptional
       | tei_model.global
       | tei_lg
      )*,
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

1.156. <licence>

<licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
header: availability
May contain
Note

A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence.

Example
<licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence </licence>
Example
<availability>  <licence target="http://creativecommons.org/licenses/by/3.0/"   notBefore="2013-01-01">   <p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence      applies to this document.</p>   <p>The licence was added on January 1, 2013.</p>  </licence> </availability>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element licence
{
   tei_att.global.attributes,
   tei_att.pointing.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.specialPara
}

1.157. <list>

<list> (list) contains any sequence of items organized as a list. [3.8. Lists]
Modulecore
Attributes
type(type) describes the nature of the items in the list.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
gloss
(gloss) each list item glosses some term or concept, which is given by a <label> element preceding the list item.
index
(index) each list item is an entry in an index such as the alphabetical topical index at the back of a print volume.
instructions
(instructions) each list item is a step in a sequence of instructions, as in a recipe.
litany
(litany) each list item is one of a sequence of petitions, supplications or invocations, typically in a religious ritual.
syllogism
(syllogism) each list item is part of an argument consisting of two or more propositions and a final conclusion derived from them.
Note

Previous versions of these Guidelines recommended the use of type on <list> to encode the rendering or appearance of a list (whether it was bulleted, numbered, etc.). The current recommendation is to use the rend or style attributes for these aspects of a list, while using type for the more appropriate task of characterizing the nature of the content of a list.

The formal syntax of the element declarations allows <label> tags to be omitted from lists tagged <list type="gloss">; this is however a semantic error.

Member of
Contained by
May contain
Note

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

Example
<list rend="numbered">  <item>a butcher</item>  <item>a baker</item>  <item>a candlestick maker, with  <list rend="bulleted">    <item>rings on his fingers</item>    <item>bells on his toes</item>   </list>  </item> </list>
Example
<list type="syllogismrend="bulleted">  <item>All Cretans are liars.</item>  <item>Epimenides is a Cretan.</item>  <item>ERGO Epimenides is a liar.</item> </list>
Example
<list type="litanyrend="simple">  <item>God save us from drought.</item>  <item>God save us from pestilence.</item>  <item>God save us from wickedness in high places.</item>  <item>Praise be to God.</item> </list>
ExampleThe following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):
<div1 type="section">  <head>Athelstan's Ordinance</head>  <list rend="numbered">   <item n="1">Concerning thieves. First, that no thief is to be spared who is caught with      the stolen goods, [if he is] over twelve years and [if the value of the goods is] over      eightpence.   <list rend="numbered">     <item n="1.1">And if anyone does spare one, he is to pay for the thief with his          wergild — and the thief is to be no nearer a settlement on that account — or to          clear himself by an oath of that amount.</item>     <item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is          not to be spared [whether younger or older than twelve].</item>     <item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may          then be redeemed with 120 shillings; and the kindred are to stand surety for him          that he will desist for ever.</item>     <item n="1.4">And if he steals after that, they are to pay for him with his wergild,          or to bring him back there.</item>     <item n="1.5">And if he steals after that, they are to pay for him with his wergild,          whether to the king or to him to whom it rightly belongs; and everyone of those who          supported him is to pay 120 shillings to the king as a fine.</item>    </list>   </item>   <item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom      no justice can be obtained, that one should order their kindred to fetch back such a      person to justice and to find him a lord in public meeting.   <list rend="numbered">     <item n="2.1">And if they then will not, or cannot, produce him on that appointed day,          he is then to be a fugitive afterwards, and he who encounters him is to strike him          down as a thief.</item>     <item n="2.2">And he who harbours him after that, is to pay for him with his wergild          or to clear himself by an oath of that amount.</item>    </list>   </item>   <item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds      his guilty man, so that the king is appealed to, is to repay the value of the goods and      120 shillings to the king; and he who appeals to the king before he demands justice as      often as he ought, is to pay the same fine as the other would have done, if he had      refused him justice.   <list rend="numbered">     <item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes          known about him, is to forfeit the slave and be liable to his wergild on the first          occasionp if he does it more often, he is to be liable to pay all that he owns.</item>     <item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been          an accessory of thieves who have committed theft, is to liable to the same.</item>    </list>   </item>   <item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to      a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is      afterwards convicted at the three-fold ordeal.</item>  </list> </div1>
Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.
Example
<p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy Cross. <list rend="simple">   <item>I, Eanbald, by the grace of God archbishop of the holy church of York, have      subscribed to the pious and catholic validity of this document with the sign of the Holy      Cross.</item>   <item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with      the sign of the Holy Cross.</item>   <item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the      sign of the Holy Cross.</item>   <item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the      sign of the Holy Cross.</item>   <item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of      the Holy Cross.</item>   <item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>   <item>I, Æthelwine, bishop, have subscribed through delegates.</item>   <item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy      Cross.</item>  </list> </p>
Schematron
<sch:rule context="tei:list[@type='gloss']"> <sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divTop"/>
   <classRef key="model.global"/>
   <elementRef key="desc" minOccurs="0"
    maxOccurs="unbounded"/>
  </alternate>
  <alternate>
   <sequence minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="item"/>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <elementRef key="headLabel"
     minOccurs="0"/>
    <elementRef key="headItem"
     minOccurs="0"/>
    <sequence minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="label"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
     <elementRef key="item"/>
     <classRef key="model.global"
      minOccurs="0" maxOccurs="unbounded"/>
    </sequence>
   </sequence>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottom"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element list
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.cmc.attributes,
   attribute type
   {
      "gloss" | "index" | "instructions" | "litany" | "syllogism"
   }?,
   (
      ( tei_model.divTop | tei_model.global | tei_desc* )*,
      (
         ( ( tei_item, tei_model.global* )+ )
       | (
            tei_headLabel?,
            tei_headItem?,
            ( ( tei_label, tei_model.global*, tei_item, tei_model.global* )+ )
         )
      ),
      ( ( tei_model.divBottom, tei_model.global* )* )
   )
}

1.158. <listBibl>

<listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.12.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 16.3.2. Declarable Elements]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<listBibl>  <head>Works consulted</head>  <bibl>Blain, Clements and Grundy: Feminist Companion to    Literature in English (Yale, 1990)  </bibl>  <biblStruct>   <analytic>    <title>The Interesting story of the Children in the Wood</title>   </analytic>   <monogr>    <title>The Penny Histories</title>    <author>Victor E Neuberg</author>    <imprint>     <publisher>OUP</publisher>     <date>1968</date>    </imprint>   </monogr>  </biblStruct> </listBibl>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.milestoneLike"
    minOccurs="1" maxOccurs="1"/>
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.milestoneLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listBibl
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.milestoneLike | tei_relation | tei_listRelation )*,
      (
         (
            tei_model.biblLike+,
            ( tei_model.milestoneLike | tei_relation | tei_listRelation )*
         )+
      )
   )
}

1.159. <listChange>

<listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 12.7. Identifying Changes and Revisions]
Moduleheader
Attributes
orderedindicates whether the ordering of its child <change> elements is to be considered significant or not
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Contained by
May contain
core: desc
Note

When this element appears within the <creation> element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text.

Example
<revisionDesc>  <listChange>   <change when="1991-11-11who="#LB"> deleted chapter 10 </change>   <change when="1991-11-02who="#MSM"> completed first draft </change>  </listChange> </revisionDesc>
Example
<profileDesc>  <creation>   <listChange ordered="true">    <change xml:id="CHG-1">First stage, written in ink by a writer</change>    <change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>    <change xml:id="CHG-3">Fixation of the revised passages and further revisions by        Goethe using ink</change>    <change xml:id="CHG-4">Addition of another stanza in a different hand,        probably at a later stage</change>   </listChange>  </creation> </profileDesc>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="listChange"/>
   <elementRef key="change"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listChange
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute ordered { text }?,
   ( tei_desc*, ( tei_listChange | tei_change )+ )
}

1.160. <listEvent>

<listEvent> (list of events) contains a list of descriptions, each of which provides information about an identifiable event. [14.3.1. Basic Principles]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listEvent>  <head>Battles of the American Civil War: Kentucky</head>  <event xml:id="event01when="1861-09-19">   <label>Barbourville</label>   <desc>The Battle of Barbourville was one of the early engagements of      the American Civil War. It occurred September 19, 1861, in Knox      County, Kentucky during the campaign known as the Kentucky Confederate      Offensive. The battle is considered the first Confederate victory in      the commonwealth, and threw a scare into Federal commanders, who      rushed troops to central Kentucky in an effort to repel the invasion,      which was finally thwarted at the <ref target="#event02">Battle of        Camp Wildcat</ref> in October.</desc>  </event>  <event xml:id="event02when="1861-10-21">   <label>Camp Wild Cat</label>   <desc>The Battle of Camp Wildcat (also known as Wildcat Mountain and Camp      Wild Cat) was one of the early engagements of the American Civil      War. It occurred October 21, 1861, in northern Laurel County, Kentucky      during the campaign known as the Kentucky Confederate Offensive. The      battle is considered one of the very first Union victories, and marked      the first engagement of troops in the commonwealth of Kentucky.</desc>  </event>  <event xml:id="event03from="1864-06-11"   to="1864-06-12">   <label>Cynthiana</label>   <desc>The Battle of Cynthiana (or Kellar’s Bridge) was an engagement      during the American Civil War that was fought on June 11 and 12, 1864,      in Harrison County, Kentucky, near the town of Cynthiana. A part of      Confederate Brigadier General John Hunt Morgan's 1864 Raid into      Kentucky, the battle resulted in a victory by Union forces over the      raiders and saved the town from capture.</desc>  </event> </listEvent>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.eventLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listEvent
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      ( ( tei_model.eventLike+, ( tei_relation | tei_listRelation )* )+ )
   )
}

1.161. <listNym>

<listNym> (list of canonical names) contains a list of nyms, that is, standardized names for any thing. [14.3.7. Names and Nyms]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of names of a particular type if convenient.

Example
<listNym type="floral">  <nym xml:id="ROSE">   <form>Rose</form>  </nym>  <nym xml:id="DAISY">   <form>Daisy</form>   <etym>Contraction of <mentioned>day's eye</mentioned>   </etym>  </nym>  <nym xml:id="HTHR">   <form>Heather</form>  </nym> </listNym>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="nym" minOccurs="1"
     maxOccurs="1"/>
    <elementRef key="listNym" minOccurs="1"
     maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listNym
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      ( ( ( tei_nym | tei_listNym )+, ( tei_relation | tei_listRelation )* )+ )
   )
}

1.162. <listObject>

<listObject> (list of objects) contains a list of descriptions, each of which provides information about an identifiable physical object. [14.3.6. Objects]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish different types of objects.

Example
<listObject>  <object xml:id="AlfredJewel">   <objectIdentifier>    <country>United Kingdom</country>    <region>Oxfordshire</region>    <settlement>Oxford</settlement>    <institution>University of Oxford</institution>    <repository>Ashmolean Museum</repository>    <collection>English Treasures</collection>    <idno type="ashmolean">AN1836p.135.371</idno>    <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>    <objectName>Alfred Jewel</objectName>   </objectIdentifier>   <physDesc>    <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>        surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. Underneath the rock crystal        is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the crystal in        place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered me made'. </p>   </physDesc>   <history>    <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and was        most likely made in <origPlace>England</origPlace>. </origin>    <provenance when="1693">The jewel was discovered in 1693 at Petherton Park, North Petherton in the English county of        Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney, where King Alfred        founded a monastery. </provenance>    <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical        Transactions of the Royal Society.</provenance>    <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in the        Ashmolean Museum in Oxford. </acquisition>   </history>  </object> </listObject>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.objectLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listObject
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      ( ( tei_model.objectLike+, ( tei_relation | tei_listRelation )* )+ )
   )
}

1.163. <listOrg>

<listOrg> (list of organizations) contains a list of elements, each of which provides information about an identifiable organization. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of organizations of a particular type if convenient.

Example
<listOrg>  <head>Libyans</head>  <org>   <orgName>Adyrmachidae</orgName>   <desc>These people have, in most points, the same customs as the Egyptians, but      use the costume of the Libyans. Their women wear on each leg a ring made of      bronze [...]</desc>  </org>  <org>   <orgName>Nasamonians</orgName>   <desc>In summer they leave their flocks and herds upon the sea-shore, and go up      the country to a place called Augila, where they gather the dates from the      palms [...]</desc>  </org>  <org>   <orgName>Garamantians</orgName>   <desc>[...] avoid all society or intercourse with their fellow-men, have no      weapon of war, and do not know how to defend themselves. [...]</desc> <!-- ... -->  </org> </listOrg>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="org" minOccurs="1"
     maxOccurs="1"/>
    <elementRef key="listOrg" minOccurs="1"
     maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listOrg
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      ( ( ( tei_org | tei_listOrg )+, ( tei_relation | tei_listRelation )* )+ )
   )
}

1.164. <listPerson>

<listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [14.3.2. The Person Element 16.2. Contextual Information 2.4. The Profile Description 16.3.2. Declarable Elements]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

The type attribute may be used to distinguish lists of people of a particular type if convenient.

Example
<listPerson type="respondents">  <personGrp xml:id="PXXX"/>  <person xml:id="P1234sex="2age="mid"/>  <person xml:id="P4332sex="1age="mid"/>  <listRelation>   <relation type="personalname="spouse"    mutual="#P1234 #P4332"/>  </listRelation> </listPerson>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.personLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPerson"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPerson
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      (
         (
            ( tei_model.personLike | tei_listPerson )+,
            ( tei_relation | tei_listRelation )*
         )+
      )
   )
}

1.165. <listPlace>

<listPlace> (list of places) contains a list of places, optionally followed by a list of relationships (other than containment) defined amongst them. [2.2.7. The Source Description 14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<listPlace type="offshoreIslands">  <place>   <placeName>La roche qui pleure</placeName>  </place>  <place>   <placeName>Ile aux cerfs</placeName>  </place> </listPlace>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="relation" minOccurs="1"
    maxOccurs="1"/>
   <elementRef key="listRelation"
    minOccurs="1" maxOccurs="1"/>
  </alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <classRef key="model.placeLike"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listPlace"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element listPlace
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.declarable.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_relation | tei_listRelation )*,
      (
         (
            ( tei_model.placeLike | tei_listPlace )+,
            ( tei_relation | tei_listRelation )*
         )+
      )
   )
}

1.166. <listPrefixDef>

<listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in teidata.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
Member of
Contained by
May contain
ExampleIn this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element.
<listPrefixDef>  <prefixDef ident="psn"   matchPattern="([A-Z]+)"   replacementPattern="personography.xml#$1">   <p> Private URIs using the <code>psn</code>      prefix are pointers to <gi>person</gi>      elements in the personography.xml file.      For example, <code>psn:MDH</code>      dereferences to <code>personography.xml#MDH</code>.   </p>  </prefixDef>  <prefixDef ident="bibl"   matchPattern="([a-z]+[a-z0-9]*)"   replacementPattern="http://www.example.com/getBibl.xql?id=$1">   <p> Private URIs using the <code>bibl</code> prefix can be      expanded to form URIs which retrieve the relevant      bibliographical reference from www.example.com.   </p>  </prefixDef> </listPrefixDef>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="prefixDef"/>
   <elementRef key="listPrefixDef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listPrefixDef
{
   tei_att.global.attributes,
   ( tei_desc*, ( tei_prefixDef | tei_listPrefixDef )+ )
}

1.167. <listRef>

<listRef> (list of references) supplies a list of significant references in the current document or elsewhere.
Moduletagdocs
Attributes
Member of
Contained by
May contain
core: desc ptr ref
tagdocs: listRef
Note

When <listRef> is used in the context of tagdocs, further restrictons apply:

  • It may only contain <ptr> or <ref> elements.
  • Each <ptr> or <ref> child should bear a target attribute, the value of which should be a single URI pointer.
Example
<listRef>  <ptr target="#ddc12"/> </listRef>
Schematron
<sch:rule context="( tei:classSpec | tei:dataSpec | tei:elementSpec | tei:macroSpec | tei:moduleSpec | tei:schemaSpec | tei:specGrp )/tei:listRef"> <sch:report test="tei:listRef">In the context of tagset documentation, the listRef element must not self-nest.</sch:report> </sch:rule>
Schematron
<sch:rule context="( tei:classSpec | tei:dataSpec | tei:elementSpec | tei:macroSpec | tei:moduleSpec | tei:schemaSpec | tei:specGrp )/tei:listRef/tei:ptr | ( tei:classSpec | tei:dataSpec | tei:elementSpec | tei:macroSpec | tei:moduleSpec | tei:schemaSpec | tei:specGrp )/tei:listRef/tei:ref"> <sch:assert test="@target and not( matches( @target,'\s') )">In the context of tagset documentation, each ptr or ref element inside a listRef must have a target attribute with only 1 pointer as its value.</sch:assert> </sch:rule>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.ptrLike"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element listRef
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   ( tei_desc*, tei_model.ptrLike+ )
}

1.168. <listRelation>

<listRelation> provides information about relationships identified amongst people, places, and organizations, either informally as prose or as formally expressed relation links. [14.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
Member of
Contained by
May contain
core: desc head p
Note

May contain a prose description organized as paragraphs, or a sequence of <relation> elements.

Example
<listPerson>  <person xml:id="pp1"> <!-- data about person pp1 -->  </person>  <person xml:id="pp2"> <!-- data about person pp1 -->  </person> <!-- more person (pp3, pp4) elements here -->  <listRelation type="personal">   <relation name="parent"    active="#pp1 #pp2passive="#pp3 #pp4"/>   <relation name="spouse"    mutual="#pp1 #pp2"/>  </listRelation>  <listRelation type="social">   <relation name="employeractive="#pp1"    passive="#pp3 #pp5 #pp6 #pp7"/>  </listRelation> </listPerson>
The persons with identifiers pp1 and pp2 are the parents of pp3 and pp4; they are also married to each other; pp1 is the employer of pp3, pp5, pp6, and pp7.
Example
<listPerson>  <person xml:id="en_pp1"> <!-- data about person en_pp1 -->  </person>  <person xml:id="en_pp2"> <!-- data about person en_pp2 -->  </person> <!-- more person (en_pp3, en_pp4) elements here --> </listPerson> <listPlace>  <place xml:id="en_pl1"> <!-- data about place en_pl1 -->  </place> <!-- more place (en_pl2, en_pl3) elements here --> </listPlace> <listRelation>  <relation name="residence"   active="#en_pp1 #en_pp2passive="#en_pl1"/> </listRelation>
The persons with identifiers en_pp1 and en_pp2 live in en_pl1.
Example
<listRelation>  <p>All speakers are members of the Ceruli family, born in Naples.</p> </listRelation>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1" maxOccurs="1">
   <classRef key="model.pLike"/>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="relation"
     minOccurs="1" maxOccurs="1"/>
    <elementRef key="listRelation"
     minOccurs="1" maxOccurs="1"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element listRelation
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   tei_att.cmc.attributes,
   (
      tei_model.headLike*,
      tei_desc*,
      ( tei_model.pLike | ( tei_relation | tei_listRelation )+ )
   )
}

1.169. <location>

<location> (location) defines the location of a place as a set of geographical coordinates, in terms of other named geo-political entities, or as an address. [14.3.4. Places]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<place>  <placeName>Abbey Dore</placeName>  <location>   <geo>51.969604 -2.893146</geo>  </location> </place>
Example
<place xml:id="BGbuildingtype="building">  <placeName>Brasserie Georges</placeName>  <location>   <country key="FR"/>   <settlement type="city">Lyon</settlement>   <district type="arrondissement">IIème</district>   <district type="quartier">Perrache</district>   <placeName type="street">    <num>30</num>, Cours de Verdun</placeName>  </location> </place>
Example
<place type="imaginary">  <placeName>Atlantis</placeName>  <location>   <offset>beyond</offset>   <placeName>The Pillars of <persName>Hercules</persName>   </placeName>  </location> </place>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="precision"/>
  <classRef key="model.labelLike"/>
  <classRef key="model.placeNamePart"/>
  <classRef key="model.offsetLike"/>
  <classRef key="model.measureLike"/>
  <classRef key="model.addressLike"/>
  <classRef key="model.noteLike"/>
  <classRef key="model.biblLike"/>
 </alternate>
</content>
    
Schema Declaration
element location
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision
    | tei_model.labelLike
    | tei_model.placeNamePart
    | tei_model.offsetLike
    | tei_model.measureLike
    | tei_model.addressLike
    | tei_model.noteLike
    | tei_model.biblLike
   )*
}

1.170. <macroRef>

<macroRef> points to the specification for some pattern which is to be included in a schema [23.7. Macro Specifications]
Moduletagdocs
Attributes
keythe identifier used for the required pattern within the source indicated.
StatusRequired
Datatypeteidata.xmlName
Member of
Contained by
May containEmpty element
Note

Patterns or macros are identified by the name supplied as value for the ident attribute on the <macroSpec> element in which they are declared. All TEI macro names are unique.

Example
<schemaSpec ident="myTEI"  source="http://www.tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.xml"> <!-- ... -->  <macroRef key="macro.paraContent"/> <!-- ... --> </schemaSpec>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element macroRef { tei_att.global.attributes, attribute key { text }, empty }

1.171. <macroSpec>

<macroSpec> (macro specification) documents the function and implementation of a pattern. [23.3. Specification Elements 23.7. Macro Specifications]
Moduletagdocs
Attributes
Member of
Contained by
May contain
Example
<macroSpec module="tei"  ident="macro.phraseSeq">  <content>   <alternate minOccurs="0"    maxOccurs="unbounded">    <textNode/>    <classRef key="model.gLike"/>    <classRef key="model.phrase"/>    <classRef key="model.global"/>   </alternate>  </content> </macroSpec>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identSynonyms"/>
   <classRef key="model.descLike"/>
  </alternate>
  <alternate minOccurs="0" maxOccurs="1">
   <elementRef key="content"/>
   <elementRef key="valList"/>
  </alternate>
  <elementRef key="constraintSpec"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="listRef" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element macroSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   (
      ( tei_model.identSynonyms | tei_model.descLike )*,
      ( tei_content | tei_valList )?,
      tei_constraintSpec*,
      tei_exemplum*,
      tei_remarks*,
      tei_listRef*
   )
}

1.172. <measure>

<measure> (measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typespecifies the type of measurement in any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Member of
Contained by
May contain
ExampleThis example references a definition of a measurement unit declared in the TEI header:
<measure type="weight">  <num>2</num> pounds of flesh </measure> <measure type="currency">£10-11-6d</measure> <measure type="areaunitRef="#merk">2 <unit>merks</unit> of old extent</measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="merktype="area">    <label>merk</label>    <placeName ref="#Scotland"/>    <desc>A merk was an area of land determined variably by its agricultural        productivity.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure quantity="40unit="hogshead"  commodity="rum">2 score hh rum</measure> <measure quantity="12unit="count"  commodity="roses">1 doz. roses</measure> <measure quantity="1unit="count"  commodity="tulips">a yellow tulip</measure>
Example
<head>Long papers.</head> <p>Speakers will be given 30 minutes each: 20 minutes for presentation, 10 minutes for discussion. Proposals should not exceed <measure max="500unit="count"   commodity="words">500    words</measure>. This presentation type is suitable for substantial research, theoretical or critical discussions.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element measure
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.measurement.attributes,
   tei_att.cmc.attributes,
   tei_att.ranging.attributes,
   attribute type { text }?,
   tei_macro.phraseSeq
}

1.173. <measureGrp>

<measureGrp> (measure group) contains a group of dimensional specifications which relate to the same object, for example the height and width of a manuscript page. [11.3.4. Dimensions]
Modulecore
Attributes
Member of
Contained by
May contain
namesdates: geo
character data
Example
<measureGrp type="leavesunit="mm">  <height scope="range">157-160</height>  <width quantity="105"/> </measureGrp> <measureGrp type="ruledAreaunit="mm">  <height scope="mostquantity="90"/>  <width scope="mostquantity="48"/> </measureGrp> <measureGrp type="boxunit="in">  <height quantity="12"/>  <width quantity="10"/>  <depth quantity="6"/> </measureGrp>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.measureLike"/>
 </alternate>
</content>
    
Schema Declaration
element measureGrp
{
   tei_att.global.attributes,
   tei_att.measurement.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   ( text | tei_model.gLike | tei_model.measureLike )*
}

1.174. <media>

<media> indicates the location of any form of external media such as an audio or video clip etc. [3.10. Graphics and Other Non-textual Components]
Modulecore
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
Derived fromatt.internetMedia
StatusRequired
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
May contain
core: desc
Note

The attributes available for this element are not appropriate in all cases. For example, it makes no sense to specify the temporal duration of a graphic. Such errors are not currently detected.

The mimeType attribute must be used to specify the MIME media type of the resource specified by the url attribute.

Example
<figure>  <media mimeType="image/pngurl="fig1.png"/>  <head>Figure One: The View from the Bridge</head>  <figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a    series of buoys strung out between them.</figDesc> </figure>
Example
<media mimeType="audio/wav"  url="dingDong.wavdur="PT10S">  <desc>Ten seconds of bellringing sound</desc> </media>
Example
<media mimeType="video/mp4"  url="clip45.mp4dur="PT45Mwidth="500px">  <desc>A 45 minute video clip to be displayed in a window 500    px wide</desc> </media>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element media
{
   tei_att.typed.attributes,
   tei_att.global.attributes,
   tei_att.media.attribute.width,
   tei_att.media.attribute.height,
   tei_att.media.attribute.scale,
   tei_att.resourced.attributes,
   tei_att.declaring.attributes,
   tei_att.timed.attributes,
   tei_att.cmc.attributes,
   attribute mimeType { list { + } },
   tei_model.descLike*
}

1.175. <meeting>

<meeting> contains the formalized descriptive title for a meeting or conference, for use in a bibliographic description for an item derived from such a meeting, or as a heading or preamble to publications emanating from it. [3.12.2.2. Titles, Authors, and Editors]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<div>  <meeting>Ninth International Conference on Middle High German Textual Criticism, Aachen,    June 1998.</meeting>  <list type="attendance">   <head>List of Participants</head>   <item>    <persName>...</persName>   </item>   <item>    <persName>...</persName>   </item> <!--...-->  </list>  <p>...</p> </div>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element meeting
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.canonical.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.limitedContent
}

1.176. <memberOf>

<memberOf> specifies class membership of the documented element or class. [23.4.3. Classification of Components]
Moduletagdocs
Attributes
keyspecifies the identifier for a class of which the documented element or class is a member or subclass
StatusOptional
Datatypeteidata.name
modespecifies the effect of this declaration on its parent module.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
add
this declaration is added to the current definitions[Default]
delete
this declaration and all of its children are removed from the current setup
maxsupplies the maximum number of times the element can occur in elements which use this model class in their content model
StatusOptional
Datatypeteidata.numeric
minsupplies the minumum number of times the element must occur in elements which use this model class in their content model
StatusOptional
Datatypeteidata.numeric
Contained by
tagdocs: classes
May containCharacter data only
Note

Elements or classes which are members of multiple (unrelated) classes will have more than one <memberOf> element, grouped by a <classes> element. If an element is a member of a class C1, which is itself a subclass of a class C2, there is no need to state this, other than in the documentation for class C1.

Any additional comment or explanation of the class membership may be provided as content for this element.

Example
<memberOf key="model.divLike"/> <memberOf key="att.identified"/>
This element will appear in any content model which references model.divLike, and will have attributes defined in att.identified (in addition to any defined explicitly for this element).
Content model
<content>
 <macroRef key="macro.xtext"/>
</content>
    
Schema Declaration
element memberOf
{
   tei_att.global.attributes,
   attribute key { text }?,
   attribute mode { "add" | "delete" }?,
   attribute max { text }?,
   attribute min { text }?,
   tei_macro.xtext
}

1.177. <mentioned>

<mentioned> marks words or phrases mentioned, not used. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
There is thus a striking accentual difference between a verbal form like <mentioned xml:id="X234xml:lang="el">eluthemen</mentioned> <gloss target="#X234">we were released,</gloss> accented on the second syllable of the word, and its participial derivative <mentioned xml:id="X235xml:lang="el">lutheis</mentioned> <gloss target="#X235">released,</gloss> accented on the last.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element mentioned
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.178. <milestone>

<milestone> (milestone) marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.

The order in which <milestone> elements are given at a given point is not normally significant.

Example
<milestone n="23ed="Launit="Dreissiger"/> ... <milestone n="24ed="AVunit="verse"/> ...
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element milestone
{
   tei_att.global.attributes,
   tei_att.milestoneUnit.attributes,
   tei_att.typed.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   empty
}

1.179. <model>

<model> describes the processing intended for a specified element. [23.5.4.1. The TEI processing model]
Moduletagdocs
Attributes
behaviournames the process or function which this processing model uses in order to produce output.
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
alternate
(default, alternate) support display of alternative visualisations, for example by displaying the preferred content, by displaying both in parallel, or by toggling between the two.
anchor
(id) create an identifiable anchor point in the output.
block
(content) create a block structure
body
(content) create the body of a document.
break
(type, label) create a line, column, or page break according to the value of type
cell
(content) create a table cell
cit
(content, source) show the content, with an indication of the source
document
(content) start a new output document
figure
(title) make a figure with the title as caption
glyph
(uri) show a character by looking up reference to a chardesc at the given URI
graphic
(url, width, height, scale, title) if url is present, uses it to display graphic, else display a placeholder image.
heading
(content, level) creates a heading.
index
(type) generate list according to type.
inline
(content, label) creates inline element out of content
link
(content, uri) create hyperlink
list
(content) create a list.
listItem
(content) create a list item.
metadata
(content) create metadata section
note
(content, place, label) create a note, often out of line, depending on the value of place; could be margin, footnote, endnote, inline
omit
do nothing, do not process children
paragraph
(content) create a paragraph out of content.
row
(content) create a table row
section
(content) create a new section of the output document
table
(content) create a table
text
(content) create literal text
title
(content) create document title
useSourceRenditionwhether to obey any rendition attribute that is present.
StatusOptional
Datatypeteidata.truthValue
Note

If the useSourceRendition attribute is not specified, or has the value false, any renditional information specified in the source document should be ignored.

outputthe intended output.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
web
the output is intended for presentation in a web format
print
the output is intended for presentation in a print format
plain
the output is intended for presentation in a plain text format
Note

If the output attribute is not specified, this model is assumed to apply for all forms of output.

cssClassthe name of a CSS class which should be associated with this element
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
Contained by
May contain
Note

The intended output to be generated for a particular behaviour of a processing model may be documented in one or all of the three following ways. Firstly, the cssClass attribute may be used to specify the name of a CSS style in some associated CSS stylesheet which is to be applied to each occurrence of a specified element found (in a given context, for a specified output). Secondly, the attribute useSourceRendition may be used to indicate that the default rendition for occurrences of this element, as defined by a <rendition> element in the document header, should be applied. Thirdly, the styling to be applied may be specified explicitly as content of a child <outputRendition> element. When more than one of these options is used, they are understood to be combined in accordance with the rules for multiple declaration of the styling language used.

Example
<model behaviour="inline"/>
Example
<elementSpec mode="changeident="quote">  <model predicate="ancestor::p"   behaviour="inline">   <desc versionDate="2015-08-21"    xml:lang="en">If it's inside a paragraph then it's      inline</desc>  </model>  <model predicate="not(ancestor::p)"   behaviour="block">   <desc versionDate="2015-08-21"    xml:lang="en">If it's not inside a paragraph then it is      block level</desc>  </model> </elementSpec>
Example
<model predicate="parent::person"  behaviour="inline">  <desc versionDate="2015-08-21"   xml:lang="en">If it is a child of a person element, treat as    inline</desc> </model>
Example
<model behaviour="inline">  <outputRendition>font-weight:bold</outputRendition> </model>
Example
<model behaviour="inlineoutput="print"/>
Example
<model predicate="ancestor::p"  behaviour="inline">  <param name="contentvalue="@n"/> </model>
Example
<elementSpec mode="changeident="date">  <model output="printpredicate="text()"   behaviour="inline"/>  <model output="print"   predicate="@when and not(text())behaviour="inline">   <param name="contentvalue="@when"/>  </model>  <model predicate="@whenoutput="web"   behaviour="alternate">   <param name="alternatevalue="@when"/>  </model> </elementSpec>
Example
<elementSpec mode="changeident="choice">  <model predicate="sic and corr"   behaviour="alternate">   <param name="defaultvalue="corr"/>   <param name="alternatevalue="sic"/>  </model>  <model predicate="abbr and expan"   behaviour="alternate">   <param name="defaultvalue="expan"/>   <param name="alternatevalue="abbr"/>  </model>  <model predicate="orig and reg"   behaviour="alternate">   <param name="defaultvalue="reg"/>   <param name="alternatevalue="orig"/>  </model> </elementSpec>
SchematronIt is ambigous to have 2 <model>s that have both the same output and have no predicate (and thus select the same set of nodes).
<sch:rule context="tei:model[ not( parent::tei:modelSequence ) ][ not( @predicate ) ]"> <sch:let name="output"  value="normalize-space( @output )"/> <sch:report test="following-sibling::tei:model [ not( @predicate )] [ normalize-space( @output ) eq $output ]"> There are 2 (or more) 'model' elements in this '<sch:value-of select="local-name(..)"/>' that have no predicate, but are targeted to the same output ("<sch:value-of select="( $output, parent::modelGrp/@output, 'all')[1]"/>")</sch:report> </sch:rule>
SchematronIt is ambigous to have 2 <model>s that have both the same output and the same predicate (and thus select the same set of nodes).
<sch:rule context="tei:model[ not( parent::tei:modelSequence ) ][ @predicate ]"> <sch:let name="predicate"  value="normalize-space( @predicate )"/> <sch:let name="output"  value="normalize-space( @output )"/> <sch:report test="following-sibling::tei:model [ normalize-space( @predicate ) eq $predicate ] [ normalize-space( @output ) eq $output ]"> There are 2 (or more) 'model' elements in this '<sch:value-of select="local-name(..)"/>' that have the same predicate, and are targeted to the same output ("<sch:value-of select="( $output, parent::modelGrp/@output, 'all')[1]"/>")</sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identEquiv"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="param" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="outputRendition"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element model
{
   tei_att.global.attributes,
   tei_att.predicate.attributes,
   attribute behaviour
   {
      "alternate"
    | "anchor"
    | "block"
    | "body"
    | "break"
    | "cell"
    | "cit"
    | "document"
    | "figure"
    | "glyph"
    | "graphic"
    | "heading"
    | "index"
    | "inline"
    | "link"
    | "list"
    | "listItem"
    | "metadata"
    | "note"
    | "omit"
    | "paragraph"
    | "row"
    | "section"
    | "table"
    | "text"
    | "title"
   },
   attribute useSourceRendition { text }?,
   attribute output { text }?,
   attribute cssClass { list { + } }?,
   (
      ( tei_model.identEquiv | tei_model.descLike )*,
      tei_param*,
      tei_outputRendition*
   )
}

1.180. <modelGrp>

<modelGrp> (model group) any grouping of <model> or <modelSequence> elements with a common output method [23.5.4.4. Model Contexts and Outputs]
Moduletagdocs
Attributes
useSourceRenditionwhether to obey any rendition attribute which is present
StatusOptional
Datatypeteidata.truthValue
outputthe intended output method
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
web
the output is intended for presentation in a web format
print
the output is intended for presentation in a print format
plaintext
the output is intended for presentation in a plain text format
Contained by
tagdocs: elementSpec
May contain
Note

The child <model> elements of a <modelGrp> are always processed independently.

Example
<elementSpec mode="changeident="abbr">  <modelGrp output="web">   <model predicate="parent::choice"    behaviour="omit"/>   <model predicate="ancestor::front"    behaviour="inline">    <outputRendition>font-style:italic; </outputRendition>   </model>   <model predicate="not(parent::choice)"    behaviour="inline">    <outputRendition scope="before">content: ' ('</outputRendition>    <outputRendition scope="after">content: ')'</outputRendition>   </model>  </modelGrp>  <modelGrp output="print">   <model predicate="parent::choice"    behaviour="omit"/>   <model predicate="not(parent::choice)"    behaviour="note">    <param name="placevalue="'foot'"/>   </model>  </modelGrp> </elementSpec>
Example
<modelGrp output="print">  <modelSequence>   <model behaviour="inline">    <param name="contentvalue="@n"/>   </model>   <model behaviour="note">    <param name="placevalue="'foot'"/>   </model>  </modelSequence> </modelGrp>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identEquiv"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="outputRendition"
   minOccurs="0"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="modelSequence"/>
   <elementRef key="model"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element modelGrp
{
   tei_att.global.attributes,
   attribute useSourceRendition { text }?,
   attribute output { "web" | "print" | "plaintext" }?,
   (
      ( tei_model.identEquiv | tei_model.descLike )*,
      tei_outputRendition?,
      ( tei_modelSequence | tei_model )+
   )
}

1.181. <modelSequence>

<modelSequence> any sequence of model or <modelSequence> elements which is to be processed as a single set of actions [23.5.4.7. Model sequence]
Moduletagdocs
Attributes
predicatethe condition under which this model applies given as an XPath Predicate Expression
StatusOptional
Datatypeteidata.xpath
useSourceRenditionwhether to obey any rendition attribute that is present
StatusOptional
Datatypeteidata.truthValue
outputthe intended output method
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
web
the output is intended for presentation in a web format
print
the output is intended for presentation in a print format
plaintext
the output is intended for presentation in a plain text format
Contained by
May contain
core: desc gloss
tagdocs: equiv model
Note

All of the <model> elements inside a <modelSequence> element must be processed. The operations indicated by each <model> child cannot be dependent on any other operation in the sequence. The results must be rendered in the order given by the list of <model>s in the <modelSequence>.

Example
<modelGrp output="print">  <modelSequence>   <model behaviour="inline">    <param name="contentvalue="@n"/>   </model>   <model behaviour="footnote">    <param name="placevalue="'foot'"/>   </model>  </modelSequence> </modelGrp>
Schematron
<sch:rule context="tei:modelSequence"> <sch:report test="tei:model[@output]"  role="warning">The 'model' children of a 'modelSequence' element inherit the @output attribute of the parent 'modelSequence', and thus should not have their own</sch:report> </sch:rule>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identEquiv"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="model" minOccurs="2"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element modelSequence
{
   tei_att.global.attributes,
   attribute predicate { text }?,
   attribute useSourceRendition { text }?,
   attribute output { "web" | "print" | "plaintext" }?,
   (
      ( tei_model.identEquiv | tei_model.descLike )*,
      ( tei_model, tei_model, tei_model* )
   )
}

1.182. <moduleRef>

<moduleRef> (module reference) references a module which is to be incorporated into a schema. [23.2. Modules and Schemas]
Moduletagdocs
Attributes
prefixspecifies a default prefix which will be prepended to all patterns from the imported module
StatusOptional
Datatype0–1 occurrences of teidata.xmlName separated by whitespace
Schematron
<sch:rule context="tei:moduleRef"> <sch:report test="//*[ not( generate-id(.) eq generate-id( current() ) ) ]/@prefix = @prefix">The prefix attribute of <sch:name/> should not match that of any other element (it would defeat the purpose)</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:moduleRef"> <sch:report test="@except and @include">It is an error to supply both the @include and @except attributes</sch:report> </sch:rule>
Note

Use of this attribute avoids name collisions (and thus invalid schemas) when the external schema being mixed in with TEI uses a name the TEI or some other included external schema already uses for a pattern.

includesupplies a list of the elements which are to be copied from the specified module into the schema being defined.
StatusOptional
Datatype0–∞ occurrences of teidata.xmlName separated by whitespace
exceptsupplies a list of the elements which are not to be copied from the specified module into the schema being defined.
StatusOptional
Datatype0–∞ occurrences of teidata.xmlName separated by whitespace
keythe name of a TEI module
StatusOptional
Datatypeteidata.xmlName
url(uniform resource locator) refers to a non-TEI module of RELAX NG code by external location
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
tagdocs: content
Note

If neither include nor except is supplied, the effect of this element is to make all the declarations contained by the referenced module available to the schema being compiled. If both attributes are supplied, an ODD processor should signal an error.

A TEI module is identified by the name supplied as value for the ident attribute on a <moduleSpec> element. The source attribute may be used to specify an online source from which the specification of that module may be read. A URI may alternatively be supplied in the case of a non-TEI module, and this is expected to be written as a RELAX NG schema.

If the url attribute is used, the <content> element may also be supplied as a child of this element. Its content (which is assumed to be a fragment of RELAX NG code) will be copied along with the content of the resource indicated by the url attribute into the target RELAX NG schema.

Example
<moduleRef key="linking"/>
This includes all objects available from the linking module.
Example
<moduleRef key="linking"  except="linkGrp link"/>
This includes all elements available from the linking module except for the <link> and <linkGrp> elements.
Example
<moduleRef key="linking"  include="linkGrp link"/>
This includes only the <link> and <linkGrp> elements from the linking module.
Schematron
<sch:rule context="tei:moduleRef"> <sch:report test="* and @key"> Child elements of <sch:name/> are only allowed when an external module is being loaded </sch:report> </sch:rule>
Content model
<content>
 <elementRef key="content" minOccurs="0"/>
</content>
    
Schema Declaration
element moduleRef
{
   tei_att.global.attributes,
   attribute prefix { ? }?,
   ( attribute include { list { * } }? | attribute except { list { * } }? ),
   ( attribute key { text }? | attribute url { text }? ),
   tei_content?
}

1.183. <moduleSpec>

<moduleSpec> (module specification) documents the structure, content, and purpose of a single module, i.e. a named and externally visible group of declarations. [23.2. Modules and Schemas]
Moduletagdocs
Attributes
Member of
Contained by
May contain
core: desc gloss
header: idno
Example
<moduleSpec ident="namesdates">  <idno type="FPI">Names and Dates</idno>  <desc>Additional elements for names and dates</desc> </moduleSpec>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identEquiv"/>
   <elementRef key="idno"/>
   <classRef key="model.descLike"/>
  </alternate>
  <elementRef key="exemplum" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="remarks" minOccurs="0"/>
  <elementRef key="listRef" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element moduleSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.typed.attributes,
   (
      ( tei_model.identEquiv | tei_idno | tei_model.descLike )*,
      tei_exemplum*,
      tei_remarks?,
      tei_listRef*
   )
}

1.184. <monogr>

<monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Contained by
May contain
Note

May contain specialized bibliographic elements, in a prescribed order.

The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item.

Example
<biblStruct>  <analytic>   <author>Chesnutt, David</author>   <title>Historical Editions in the States</title>  </analytic>  <monogr>   <title level="j">Computers and the Humanities</title>   <imprint>    <date when="1991-12">(December, 1991):</date>   </imprint>   <biblScope>25.6</biblScope>   <biblScope unit="pagefrom="377to="380">377–380</biblScope>  </monogr> </biblStruct>
Example
<biblStruct type="book">  <monogr>   <author>    <persName>     <forename>Leo Joachim</forename>     <surname>Frachtenberg</surname>    </persName>   </author>   <title type="mainlevel="m">Lower Umpqua Texts</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Columbia University Press</publisher>    <date>1914</date>   </imprint>  </monogr>  <series>   <title type="mainlevel="s">Columbia University Contributions to      Anthropology</title>   <biblScope unit="volume">4</biblScope>  </series> </biblStruct>
Content model
<content>
 <sequence>
  <alternate minOccurs="0">
   <sequence>
    <alternate>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
    <elementRef key="title" minOccurs="1"
     maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
     <elementRef key="textLang"/>
     <elementRef key="editor"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <elementRef key="title"/>
     <classRef key="model.ptrLike"/>
     <elementRef key="idno"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="textLang"/>
     <elementRef key="author"/>
     <elementRef key="editor"/>
     <elementRef key="meeting"/>
     <elementRef key="respStmt"/>
    </alternate>
   </sequence>
   <sequence>
    <elementRef key="authority"/>
    <elementRef key="idno"/>
   </sequence>
  </alternate>
  <elementRef key="availability"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.noteLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="edition"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <classRef key="model.ptrLike"/>
    <elementRef key="editor"/>
    <elementRef key="sponsor"/>
    <elementRef key="funder"/>
    <elementRef key="respStmt"/>
   </alternate>
  </sequence>
  <elementRef key="imprint"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <elementRef key="imprint"/>
   <elementRef key="extent"/>
   <elementRef key="biblScope"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element monogr
{
   tei_att.global.attributes,
   (
      (
         (
            ( tei_author | tei_editor | tei_meeting | tei_respStmt ),
            ( tei_author | tei_editor | tei_meeting | tei_respStmt )*,
            tei_title+,
            (
               tei_model.ptrLike
             | tei_idno
             | tei_textLang
             | tei_editor
             | tei_respStmt
            )*
         )
       | (
            ( tei_title | tei_model.ptrLike | tei_idno )+,
            (
               tei_textLang
             | tei_author
             | tei_editor
             | tei_meeting
             | tei_respStmt
            )*
         )
       | ( tei_authority, tei_idno )
      )?,
      tei_availability*,
      tei_model.noteLike*,
      (
         (
            tei_edition,
            (
               tei_idno
             | tei_model.ptrLike
             | tei_editor
             | tei_sponsor
             | tei_funder
             | tei_respStmt
            )*
         )*
      ),
      tei_imprint,
      ( tei_imprint | tei_extent | tei_biblScope )*
   )
}

1.185. <name>

<name> (name, proper noun) contains a proper noun or noun phrase. [3.6.1. Referring Strings]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included.

Example
<name type="person">Thomas Hoccleve</name> <name type="place">Villingaholt</name> <name type="org">Vetus Latina Institut</name> <name type="personref="#HOC001">Occleve</name>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element name
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.187. <namespace>

<namespace> (namespace) supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
namespecifies the full formal name of the namespace concerned.
StatusRequired
Datatype0–1 occurrences of teidata.namespace separated by whitespace
Contained by
header: tagsDecl
May contain
header: tagUsage
Example
<namespace name="http://www.tei-c.org/ns/1.0">  <tagUsage gi="hioccurs="28withId="2"> Used only to mark English words    italicized in the copy text </tagUsage> </namespace>
Content model
<content>
 <elementRef key="tagUsage" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element namespace
{
   tei_att.global.attributes,
   attribute name { ? },
   tei_tagUsage+
}

1.188. <nationality>

<nationality> (nationality) contains an informal description of a person's present or past nationality or citizenship. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
birth
naturalised
self-assigned
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<nationality key="USnotBefore="1966"> Obtained US Citizenship in 1966</nationality>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element nationality
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.189. <normalization>

<normalization> (normalization) indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
methodindicates the method adopted to indicate normalizations within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
silent
normalization made silently[Default]
markup
normalization represented using markup
Member of
Contained by
May contain
core: p
Example
<editorialDecl>  <normalization method="markup">   <p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern      20th century typographical practice, the <gi>choice</gi> element has been used to      enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values      respectively. ... </p>  </normalization>  <normalization method="silent">   <p>Spacing between words and following punctuation has been regularized to zero spaces;      spacing between words has been regularized to one space.</p>  </normalization>  <normalization source="http://www.dict.sztaki.hu/webster">   <p>Spelling converted throughout to Modern American usage, based on Websters 9th      Collegiate dictionary.</p>  </normalization> </editorialDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element normalization
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute method { "silent" | "markup" }?,
   tei_model.pLike+
}

1.190. <note>

<note> (note) contains a note or annotation. [3.9.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.12.2.8. Notes and Statement of Language 10.3.5.4. Notes within Entries]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIn the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note place="bottomtype="gloss"  resp="#MDMH">  <term xml:lang="de">Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <mentioned>picturesque</mentioned> and <mentioned>painterly</mentioned> respectively. </note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. <!-- elsewhere in the document --> <respStmt xml:id="MDMH">  <resp>translation from German to English</resp>  <name>Hottinger, Marie Donald Mackie</name> </respStmt>
For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header.
ExampleThe global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:
Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n="126anchored="true"> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann.
However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element note
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   tei_att.anchoring.attributes,
   tei_att.cmc.attributes,
   tei_macro.specialPara
}

1.191. <noteGrp>

<noteGrp> (note group) contains a group of notes [3.9.1.1. Encoding Grouped Notes]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIn the following example, there are two notes in different languages, each specifying the content of the annotation relating to the same fragment of text:
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus <noteGrp>   <note xml:lang="en">Quatuor Tempora, so called dry fast days (Wednesday, Friday, and Saturday)      falling on each of the quarters of the year. In the first quarter they were called Cinerum      (following Ash Wednesday), second Spiritus (following Pentecost), third Crucis      (after the Exaltation of the Holy Cross, September 14th), and Luciae      in the fourth (after the feast of St. Lucia, December 13th).   </note>   <note xml:lang="pl">Quatuor Tempora, tzw. Suche dni postne (środa, piątek i sobota)      przypadające cztery razy w roku. W pierwszym kwartale zwały się Cinerum      (po Popielcu), w drugim Spiritus (po Zielonych Świętach), w trzecim Crucis      (po święcie Podwyższenia Krzyża 14 września), w czwartym Luciae      (po dniu św. Łucji 13 grudnia).   </note>  </noteGrp> totaliter expediui. </p>
Content model
<content>
 <sequence>
  <elementRef key="desc" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <elementRef key="note"/>
   <elementRef key="noteGrp"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element noteGrp
{
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   tei_att.anchoring.attributes,
   tei_att.cmc.attributes,
   ( tei_desc*, ( tei_note | tei_noteGrp )+ )
}

1.192. <notesStmt>

<notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Note

Information of different kinds should not be grouped together into the same note.

Example
<notesStmt>  <note>Historical commentary provided by Mark Cohen</note>  <note>OCR scanning done at University of Toronto</note> </notesStmt>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.noteLike"/>
  <elementRef key="relatedItem"/>
 </alternate>
</content>
    
Schema Declaration
element notesStmt
{
   tei_att.global.attributes,
   ( tei_model.noteLike | tei_relatedItem )+
}

1.193. <num>

<num> (number) contains a number, written in any form. [3.6.3. Numbers and Measures]
Modulecore
Attributes
typeindicates the type of numeric value.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cardinal
absolute number, e.g. 21, 21.5
ordinal
ordinal number, e.g. 21st
fraction
fraction, e.g. one half or three-quarters
percentage
a percentage
Note

If a different typology is desired, other values can be used for this attribute.

valuesupplies the value of the number in standard form.
StatusOptional
Datatypeteidata.numeric
Valuesa numeric value.
Note

The standard form used is defined by the TEI datatype teidata.numeric.

Member of
Contained by
May contain
Note

Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 19. Feature Structures. The <num> element is intended for use in simple applications.

Example
<p>I reached <num type="cardinalvalue="21">twenty-one</num> on my <num type="ordinalvalue="21">twenty-first</num> birthday</p> <p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>  </num> cm per second.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element num
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.ranging.attributes,
   tei_att.cmc.attributes,
   attribute type { "cardinal" | "ordinal" | "fraction" | "percentage" }?,
   attribute value { text }?,
   tei_macro.phraseSeq
}

1.194. <nym>

<nym> (canonical name) contains the definition for a canonical name or name component of any kind. [14.3.7. Names and Nyms]
Modulenamesdates
Attributes
partspoints to constituent nyms
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
namesdates: listNym nym
May contain
core: p
header: idno
namesdates: nym
Example
<nym xml:id="J452">  <form>   <orth xml:lang="en-US">Ian</orth>   <orth xml:lang="en-x-Scots">Iain</orth>  </form> </nym>
Content model
<content>
 <sequence>
  <elementRef key="idno" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.entryPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.pLike" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="nym" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element nym
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.sortable.attributes,
   attribute parts { list { + } }?,
   ( tei_idno*, tei_model.entryPart*, tei_model.pLike*, tei_nym* )
}

1.195. <object>

<object> contains a description of a single identifiable physical object. [14.3.6. Objects]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: event listObject object
May contain
Note

The <object> element is a recent addition to the TEI P5 Guidelines as of version 3.5.0 and as such may be more prone to further revision in the next few releases as its use develops. This may be particularly evident where its contents have been borrowed from <msDesc> and have yet to be generalized from their use in the context of manuscript descriptions.

The <object> element may be used for describing any object, text-bearing or not, though where the textuality of the object is the primary concern or a collection is mostly composed of manuscripts, encoders may prefer the <msDesc> element (a more specific form of <object>) which may be used not only to describe manuscripts but any form of text-bearing objects such as early printed books.

Example
<listObject>  <object xml:id="Alfred_Jewel">   <objectIdentifier>    <country>United Kingdom</country>    <region>Oxfordshire</region>    <settlement>Oxford</settlement>    <institution>University of Oxford</institution>    <repository>Ashmolean Museum</repository>    <collection>English Treasures</collection>    <idno type="ashmolean">AN1836p.135.371</idno>    <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>    <objectName>Alfred Jewel</objectName>   </objectIdentifier>   <physDesc>    <p> The Alfred Jewel is about 6.4 cm in length and is made of combination of filigreed <material>gold</material>        surrounding a polished teardrop shaped piece of transparent <material>quartz</material>. Underneath the rock        crystal is a cloisonné enamel image of a man with ecclesiastical symbols. The sides of the jewel holding the        crystal in place contain an openwork inscription saying "AELFRED MEC HEHT GEWYRCAN", meaning 'Alfred ordered        me made'. </p>   </physDesc>   <history>    <origin>It is generally accepted that the Alfred Jewel dates from the <origDate>late 9th Century</origDate> and        was most likely made in <origPlace>England</origPlace>. </origin>    <provenance when="1693">The jewel was discovered in 1693 at Petherton Park, North Petherton in the English        county of Somerset, on land owned by Sir Thomas Wroth. North Petherton is about 8 miles away from Athelney,        where King Alfred founded a monastery. </provenance>    <provenance when="1698">A description of the Alfred Jewel was first published in 1698, in the Philosophical        Transactions of the Royal Society.</provenance>    <acquisition> It was bequeathed to Oxford University by Colonel Nathaniel Palmer (c. 1661-1718) and today is in        the Ashmolean Museum in Oxford. </acquisition>   </history>  </object> </listObject> <!-- Elsewhere in document --> <p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the <objectName ref="#Alfred_Jewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster    Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>. </p>
Example
<listObject>  <object xml:id="MaskOfTutankhamun">   <objectIdentifier>    <objectName xml:lang="en">Mask of Tutankhamun</objectName>    <idno type="carter">256a</idno>    <idno type="JournalD'Entrée">60672</idno>    <idno type="exhibition">220</idno>    <institution>Museum of Egyptian Antiquities</institution>    <address>     <street>15 Meret Basha</street>     <district>Ismailia</district>     <settlement>Cairo</settlement>     <country>Egypt</country>     <location>      <geo>30.047778 31.233333</geo>     </location>    </address>   </objectIdentifier>   <msContents>    <p>The back and shoulders of the mask is inscribed with a protective spell in Egyptian hieroglyphs formed of ten        vertical and horizontal lines. This spell first appeared on masks in the Middle Kingdom at least 500 years        before Tutankhamun, and comes from chapter 151 of the <title>Book of the Dead</title>.</p>   </msContents>   <physDesc>    <p> The mask of Tutankhamun is 54cm x 39.3cm x 49cm. It is constructed from two layers of high-karat gold that        varies in thickness from 1.5-3mm. It weighs approximately 10.23kg and x-ray crystallography shows that it is        composed of two alloys of gold with a lighter 18.4 karat shade being used for the face and neck while a heavier        22.5 karat gold was used for the rest of the mask.</p>    <p>In the mask Tutankhamun wears a nemes headcloth which has the royal insignia of a cobra (Wadjet) and vulture        (Nekhbet) on it. These are thought respectively to symbolize Tutankhamun's rule of both Lower Egypt and Upper        Egypt. His ears are pierced for earrings. The mask has rich inlays of coloured glass and gemstones, including        lapis lazuli surrounding the eye and eyebrows, quartz for the eyes, obsidian for the pupils. The broad collar is        made up of carnelian, feldspar, turquoise, amazonite, faience and other stones.</p>   </physDesc>   <history>    <origin>     <p>The mask of Tutankhamun was created in <origPlace>Egypt</origPlace> around <origDate when="-1323type="circa">1323 BC</origDate>. It is a death mask of the 18th-dynasty ancient Egyptian Pharaoh Tutankhamun          who reigned 1332–1323 BC. </p>    </origin>    <provenance>     <p>The mask of Tutankhamun was found in his burial chamber at Theban Necropolis in the Valley of the Kings in          1922. On 28 October 1925 the excavation team led by English archaeologist Howard Carter opened the heavy          sarcophagus and three coffins and were the first people in around 3,250 years to see the mask of Tutankhamun.          Carter wrote in his diary: <quote> The pins removed, the lid was raised. The penultimate scene was disclosed –            a very neatly wrapped mummy of the young king, with golden mask of sad but tranquil expression, symbolizing            Osiris … the mask bears that god's attributes, but the likeness is that of Tut.Ankh.Amen – placid and            beautiful, with the same features as we find upon his statues and coffins. The mask has fallen slightly            back, thus its gaze is straight up to the heavens. </quote>     </p>    </provenance>    <acquisition> In December 1925, the mask was removed from the tomb, placed in a crate and transported 635        kilometres (395 mi) to the Egyptian Museum in Cairo, where it remains on public display. </acquisition>   </history>   <additional>    <adminInfo>     <custodialHist>      <custEvent when="1944">When it was discovered in 1925, the 2.5kg narrow gold beard was no longer attached to            the mask and was reattached to the chin by use of a wooden dowel in 1944.</custEvent>      <custEvent when="2014-08"> In August 2014 when the mask was removed from its display case for cleaning, the            beard fell off again. Those working in the museum unadvisedly used a quick-drying epoxy to attempt to fix            it, but left the beard off-centre. </custEvent>      <custEvent when="2015-01">The damage was noticed and repaired in January 2015 by a German-Egyptian team who            used beeswax, a material known to be used as adhesives by the ancient Egyptians.</custEvent>     </custodialHist>    </adminInfo>   </additional>  </object> </listObject>
Content model
<content>
 <sequence>
  <elementRef key="objectIdentifier"
   minOccurs="1" maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="msContents"/>
    <elementRef key="physDesc"/>
    <elementRef key="history"/>
    <elementRef key="additional"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <elementRef key="object" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element object
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   tei_att.declaring.attributes,
   tei_att.docStatus.attributes,
   tei_att.canonical.attributes,
   (
      tei_objectIdentifier+,
      tei_model.headLike*,
      ( tei_model.pLike+ | ( msContents | physDesc | history | additional )* ),
      ( tei_model.noteLike | tei_model.biblLike | linkGrp | link )*,
      tei_object*
   )
}

1.196. <objectIdentifier>

<objectIdentifier> (object identifier) groups one or more identifiers or pieces of locating information concerning a single object. [14.3.6. Objects]
Modulenamesdates
Attributes
Member of
Contained by
core: bibl
namesdates: object
May contain
Example
<objectIdentifier>  <country>United Kingdom</country>  <region>Oxfordshire</region>  <settlement>Oxford</settlement>  <institution>University of Oxford</institution>  <repository>Ashmolean Museum</repository>  <collection>English Treasures</collection>  <idno type="ashmolean">AN1836p.135.371</idno>  <idno type="wikipedia">https://en.wikipedia.org/wiki/Alfred_Jewel</idno>  <objectName>Alfred Jewel</objectName> </objectIdentifier>
Example
<object xml:id="Excalibur-MultipleNames">  <objectIdentifier>   <objectName type="main">Excalibur</objectName>   <objectName type="alt">Caliburn</objectName>   <objectName xml:lang="cy">Caledfwlch</objectName>   <objectName xml:lang="cnx">Calesvol</objectName>   <objectName xml:lang="br">Kaledvoulc'h</objectName>   <objectName xml:lang="la">Caliburnus</objectName>   <country>Wales</country>  </objectIdentifier>  <p>Excalibur is the name for the legendary sword of King Arthur, in Welsh it is called Caledfwlch,    in Cornish it is called Calesvol, in Breton it is called Kaledvoulc'h, and in Latin it is called Caliburnus.    In some versions Excalibur's blade was engraved with phrases on opposite sides which in translation read:    "Take me up" and "Cast me away" (or similar).</p> </object>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.placeNamePart"/>
  <elementRef key="institution"/>
  <elementRef key="repository"/>
  <elementRef key="collection"/>
  <elementRef key="idno"/>
  <elementRef key="msName"/>
  <elementRef key="objectName"/>
  <elementRef key="altIdentifier"/>
  <elementRef key="address"/>
 </alternate>
</content>
    
Schema Declaration
element objectIdentifier
{
   tei_att.global.attributes,
   (
      tei_model.placeNamePart
    | institution
    | repository
    | collection
    | tei_idno
    | msName
    | tei_objectName
    | altIdentifier
    | tei_address
   )+
}

1.197. <objectName>

<objectName> (name of an object) contains a proper noun or noun phrase used to refer to an object. [14.2.5. Object Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<p> The <objectName ref="#MinsterLovellJewel">Minster Lovell Jewel</objectName> is probably the most similar to the <objectName ref="#AlfredJewel">Alfred Jewel</objectName> and was found in <placeName ref="#MinsterLovell">Minster    Lovell</placeName> in <placeName ref="#Oxfordshire">Oxfordshire</placeName> and is kept at the <orgName ref="#AshmoleanMuseum">Ashmolean Museum</orgName>. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element objectName
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.198. <occupation>

<occupation> (occupation) contains an informal description of a person's trade, profession or occupation. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
primary
other
paid
unpaid
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
schemeindicates the classification system or taxonomy in use, for example by supplying the identifier of a <taxonomy> element, or pointing to some other resource.
StatusOptional
Datatypeteidata.pointer
codeidentifies an occupation code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<occupation>accountant</occupation>
Example
<occupation scheme="#occupationtaxonomy"  code="#acc">accountant</occupation>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element occupation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute scheme { text }?,
   attribute code { text }?,
   tei_macro.specialPara
}

1.199. <offset>

<offset> (offset) marks that part of a relative temporal or spatial expression which indicates the direction of the offset between the two place names, dates, or times involved in the expression. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName key="NRPA1">  <offset>50 metres below the summit of</offset>  <geogName>   <geogFeat>Mount</geogFeat>   <name>Sinai</name>  </geogName> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element offset
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.200. <opener>

<opener> (opener) groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<opener>  <dateline>Walden, this 29. of August 1592</dateline> </opener>
Example
<opener>  <dateline>   <name type="place">Great Marlborough Street</name>   <date>November 11, 1848</date>  </dateline>  <salute>My dear Sir,</salute> </opener> <p>I am sorry to say that absence from town and other circumstances have prevented me from earlier enquiring...</p>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <elementRef key="argument"/>
  <elementRef key="byline"/>
  <elementRef key="dateline"/>
  <elementRef key="epigraph"/>
  <elementRef key="salute"/>
  <elementRef key="signed"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element opener
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_argument
    | tei_byline
    | tei_dateline
    | tei_epigraph
    | tei_salute
    | tei_signed
    | tei_model.global
   )*
}

1.201. <org>

<org> (organization) provides information about an identifiable organization such as a business, a tribe, or any other grouping of people. [14.3.3. Organizational Data]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the organization.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, familyGroup, or politicalParty, each of which should be associated with a definition. Such local definitions will typically be provided by a <desc> for each <valItem> element in the schema specification of the project's customization.

Member of
Contained by
May contain
Example
<org xml:id="JAMs">  <orgName>Justified Ancients of Mummu</orgName>  <desc>An underground anarchist collective spearheaded by  <persName>Hagbard Celine</persName>, who fight the Illuminati    from a golden submarine, the <name>Leif Ericson</name>  </desc>  <bibl>   <author>Robert Shea</author>   <author>Robert Anton Wilson</author>   <title>The Illuminatus! Trilogy</title>  </bibl> </org>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.nameLike"/>
    <classRef key="model.placeLike"/>
    <classRef key="model.orgPart"/>
    <classRef key="model.milestoneLike"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
   <elementRef key="ptr"/>
  </alternate>
  <classRef key="model.personLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element org
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   attribute role { list { + } }?,
   (
      tei_model.headLike*,
      (
         tei_model.pLike*
       | (
            tei_model.labelLike
          | tei_model.nameLike
          | tei_model.placeLike
          | tei_model.orgPart
          | tei_model.milestoneLike
         )*
      ),
      ( tei_model.noteLike | tei_model.biblLike | linkGrp | link | tei_ptr )*,
      tei_model.personLike*
   )
}

1.202. <orgName>

<orgName> (organization name) contains an organizational name. [14.2.2. Organizational Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
About a year back, a question of considerable interest was agitated in the <orgName key="PAS1type="voluntary">  <placeName key="PEN">Pennsyla.</placeName> Abolition Society </orgName> [...]
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element orgName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.203. <orig>

<orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the original version in the copy text, <orig> may be used alone:
<l>But this will be a <orig>meere</orig> confusion</l> <l>And hardly shall we all be <orig>vnderstoode</orig> </l>
ExampleMore usually, an <orig> will be combined with a regularized form within a <choice> element:
<l>But this will be a <choice>   <orig>meere</orig>   <reg>mere</reg>  </choice> confusion</l> <l>And hardly shall we all be <choice>   <orig>vnderstoode</orig>   <reg>understood</reg>  </choice> </l>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element orig
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.204. <outputRendition>

<outputRendition> describes the rendering or appearance intended for all occurrences of an element in a specified context for a specified type of output.
Moduletagdocs
Attributes
scopeprovides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
first-line
styling applies to the first line of the target element.
first-letter
styling applies to the first character of the target element.
before
styling should be applied immediately before the content of the target element.
after
styling should be applied immediately after the content of the target element.
Member of
Contained by
May containCharacter data only
Note

This component of an element specification describes the rendering or appearance intended for all occurrences of the element in a specified context for a specified type of output. The <rendition> element, by contrast, describes the actual rendering or appearance of all occurrences of the specified element in a source document. The useSourceRendition attribute may however be used to indicate that formatting information provided by a <rendition> element is to be combined with any provided by an <outputRendition> element.

It is strongly recommended that the W3C Cascading Stylesheet language (CSS2 or later) be used to express the required formatting information.

Example
<model predicate="ancestor::p"  behaviour="inline">  <outputRendition>font-style: italic;</outputRendition> </model> <model behaviour="block">  <outputRendition>left-margin: 2em;</outputRendition> </model>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element outputRendition
{
   tei_att.global.attributes,
   attribute scope { text }?,
   text
}

1.205. <p>

<p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you    done?</q> </p> <p>  <q>I have now arranged that you can be married a second time,</q> replied Thjostolf. </p> <p>  <q>Then you must mean that Thorvald is dead,</q> she said. </p> <p>  <q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q> </p>
Schematron
<sch:rule context="tei:p"> <sch:report test="(ancestor::tei:ab or ancestor::tei:p) and not( ancestor::tei:floatingText | parent::tei:exemplum | parent::tei:item | parent::tei:note | parent::tei:q | parent::tei:quote | parent::tei:remarks | parent::tei:said | parent::tei:sp | parent::tei:stage | parent::tei:cell | parent::tei:figure )"> Abstract model violation: Paragraphs may not occur inside other paragraphs or ab elements. </sch:report> </sch:rule>
Schematron
<sch:rule context="tei:p"> <sch:report test="( ancestor::tei:l or ancestor::tei:lg ) and not( ancestor::tei:floatingText | parent::tei:figure | parent::tei:note )"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab, unless p is a child of figure or note, or is a descendant of floatingText. </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element p
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.fragmentable.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.206. <param>

<param> provides a parameter for a model behaviour by supplying its name and an XPath expression identifying the location of its content. [23.5.4.5. Behaviours and their parameters]
Moduletagdocs
Attributes
namea name for the parameter being supplied
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
alternate
when used with behaviour alternate, a parameter of this name supplies one of the pair of possible values; for example the regularized form rather than the original form within a <choice> element.
default
when used with behaviour alternate, a parameter of this name supplies one of the pair of possible values; for example the original form rather than the regularized form within a <choice> element.
height
when used with behaviour graphic, a parameter of this name supplies a value for the height of the graphic e.g. ‘300px’, ‘50%’.
id
a parameter of this name should supply a unique identifier for the element being processed; as for example with the anchor behaviour
label
a parameter of this name should supply an expression to be used to label something, for example concat('Page ', @n) for a page break or @n for a footnote reference; typically used with the note or break behaviours
level
when used with the heading behaviour, a parameter of this name supplies a positive integer indicating the hierarchic level of a heading.
link
when used with the link behaviour, a parameter of this name should supply a URL to be used as the target of a link.
place
when used with the note behaviour, a parameter of this name should provide a string which describes the intended placement of some text; typical values include ‘margin’, ‘footnote’, ‘endnote’, ‘inline’, ‘bottom’
type
a parameter of this name can be used to categorize the specified behaviour in any way; for example the kind of break (when used with the break behaviour) or the kind of index to be generated (if used with the index behaviour) etc.
url
when used with behaviour graphic, a parameter of this name supplies a a URL indicating the graphic intended.
width
when used with behaviour graphic, a parameter of this name supplies a value for the width of the graphic e.g. ‘400px’, ‘70%’.
valuesupplies an XPath expression which when evaluated provides the value for the parameter
StatusRequired
Datatypeteidata.xpath
Contained by
tagdocs: model
May containEmpty element
Note

An implementation may require parameters other than those listed here, and is not required to follow this partial specification.

The names and datatypes of the expected parameters should be documented in the corresponding customization using a <paramSpec> element. Literal strings provided in an XPath expression should be quoted.

ExampleIn this example, which will be processed for a <choice> element which has both <sic> and <corr> child elements, the default parameter will provide the value of the child <corr> element, and the alternate parameter will provide that of the child <sic> elements. If neither <param> element was supplied, both elements would still be available to an application, but the application would need to distinguish them for itself.
<elementSpec ident="choice">  <model predicate="sic and corr"   behaviour="alternate">   <param name="defaultvalue="corr"/>   <param name="alternatevalue="sic"/>  </model> </elementSpec>
Example
<elementSpec ident="graphicmode="change">  <model behaviour="graphic">   <param name="urlvalue="@url"/>   <param name="widthvalue="@width"/>   <param name="heightvalue="@height"/>  </model> </elementSpec>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element param
{
   tei_att.global.attributes,
   attribute name
   {
      "alternate"
    | "default"
    | "height"
    | "id"
    | "label"
    | "level"
    | "link"
    | "place"
    | "type"
    | "url"
    | "width"
   },
   attribute value { text },
   empty
}

1.207. <paramList>

<paramList> list of parameter specifications
Moduletagdocs
Attributes
Contained by
tagdocs: valItem
May contain
tagdocs: paramSpec
Note

The <paramList> element provides a a mechanism to document parameter specifications using child <paramSpec> elements.

Example
<valItem ident="alternate">  <desc versionDate="2015-08-21"   xml:lang="en">create a specialized display of alternating elements for displaying the preferred version and an alternative, both at once or by some method of toggling between the two.</desc>  <paramList>   <paramSpec ident="default">    <desc>preferred content</desc>   </paramSpec>   <paramSpec ident="alternate">    <desc>alternate content</desc>   </paramSpec>  </paramList> </valItem>
Content model
<content>
 <elementRef minOccurs="0"
  maxOccurs="unbounded" key="paramSpec"/>
</content>
    
Schema Declaration
element paramList { tei_att.global.attributes, tei_paramSpec* }

1.208. <paramSpec>

<paramSpec> supplies specification for one parameter of a model behaviour [23.5.4.8. Defining a processing model]
Moduletagdocs
Attributes
Contained by
tagdocs: paramList
May contain
core: desc gloss
tagdocs: equiv
Note

Where a model behaviour uses more than one parameter, individual <paramSpec> elements should be grouped together using a <paramList> element, as above. Parameter specifications are provided within the <valItem> used to define a particular behaviour, which forms part of the specification of a <model> element's behaviour attribute. In the example above, the behaviour link has two parameters: content and link.

Using a <desc> element within a <paramSpec> is optional but recommended practice.

Example
<valItem ident="link">  <desc>create a hyperlink</desc>  <paramList>   <paramSpec ident="content">    <desc>supplies the location of some content describing the link</desc>   </paramSpec>   <paramSpec ident="link">    <desc>supplies the location of the intended URL</desc>   </paramSpec>  </paramList> </valItem>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.identEquiv"/>
  <classRef key="model.descLike"/>
 </alternate>
</content>
    
Schema Declaration
element paramSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   ( tei_model.identEquiv | tei_model.descLike )*
}

1.209. <pb>

<pb> (page beginning) marks the beginning of a new page in a paginated document. [3.11.3. Milestone Elements]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Note

A <pb> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb> element itself.

The type attribute may be used to characterize the page break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the page break is word-breaking, or to note the source from which it derives.

ExamplePage numbers may vary in different editions of a text.
<p> ... <pb n="145ed="ed2"/> <!-- Page 145 in edition "ed2" starts here --> ... <pb n="283ed="ed1"/> <!-- Page 283 in edition "ed1" starts here--> ... </p>
ExampleA page break may be associated with a facsimile image of the page it introduces by means of the facs attribute
<body>  <pb n="1facs="page1.png"/> <!-- page1.png contains an image of the page; the text it contains is encoded here -->  <p> <!-- ... -->  </p>  <pb n="2facs="page2.png"/> <!-- similarly, for page 2 -->  <p> <!-- ... -->  </p> </body>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element pb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.edition.attributes,
   tei_att.spanning.attributes,
   tei_att.breaking.attributes,
   tei_att.cmc.attributes,
   empty
}

1.210. <persName>

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person, possibly including one or more of the person's forenames, surnames, honorifics, added names, etc. [14.2.1. Personal Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<persName>  <forename>Edward</forename>  <forename>George</forename>  <surname type="linked">Bulwer-Lytton</surname>, <roleName>Baron Lytton of  <placeName>Knebworth</placeName>  </roleName> </persName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persName
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.211. <persPronouns>

<persPronouns> (personal pronouns) indicates the personal pronouns used, or assumed to be used, by the individual being described. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
evidence(evidence) indicates support for the listed personal pronouns.
StatusRecommended
Datatypeteidata.enumerated
Suggested values include:
conjecture
(conjecture) The given value was selected based on assumptions by someone besides the person to whom this pronoun applies. As a result, the value may be erroneous.
selfIdentification
(self identification) The given value has been explicitly stated or confirmed by the person to whom this pronoun applies.
trustedThirdParty
(trusted third party) The given value has been supplied by another individual trusted by the encoder to know the preferences of the person to whom this pronoun applies.
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
value(value) supplies a regularized value for personal pronouns.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Sample values include:
e
(e) e/eirs
he
(he) he/him/his
she
(she) she/her/hers
they
(they) they/them/theirs
Note

The sample values list shown here is intended to be reflective of English usage. There is nothing restricting users from defining lists reflective of other languages, e.g. elle, il, and ils.

Member of
Contained by
May contain
Example
<person>  <persName>   <forename>SUE</forename>   <addName>the T. rex</addName>  </persName>  <residence>The Field Museum. Chicago, Illinois, United States.</residence>  <sex value="0"/>  <persPronouns value="they">they/them</persPronouns>  <note>   <cit>    <quote>Specimen FMNH PR 2081. Legendary Fossil. Apex        Predator. National Treasure. <emph style="text-transform:uppercase; letter-spacing:0.25rem;">Murderbird.</emph>    </quote>    <bibl>SUEtheTrex, Twitter biography.    <ptr target="https://twitter.com/SUEtheTrex"/>.        Accessed <date when="2020-03-25">March 25th, 2020</date>.</bibl>   </cit>  </note> </person>
Example
<docAuthor>  <persName>Lal Zimman</persName>  <persPronouns value="he">(he/him/his)</persPronouns>  <ref target="#Name">(FAQ)</ref>  <persName type="IPA">[lɑɫ ˈzimn̩]</persName>  <email>zimman at ucsb dot edu</email>  <roleName>Assistant Professor of Linguistics</roleName>  <roleName>Affiliated Faculty in Feminist Studies</roleName>  <address>   <addrLine>South Hall 3518</addrLine>   <addrLine>University of California, Santa Barbara</addrLine>  </address> </docAuthor>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element persPronouns
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute evidence
   {
      "conjecture" | "selfIdentification" | "trustedThirdParty"
   }?,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   tei_macro.phraseSeq
}

1.212. <person>

<person> (person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [14.3.2. The Person Element 16.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the person.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the person.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

agespecifies an age group for the person.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
namesdates: event listPerson org
May contain
Note

May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class.

Example
<person sex="Fage="adult">  <p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic    status B2.</p> </person>
Example
<person sex="intersexrole="god"  age="immortal">  <persName>Hermaphroditos</persName>  <persName xml:lang="grc">Ἑρμαφρόδιτος</persName> </person>
Example
<person xml:id="Ovi01sex="Mrole="poet">  <persName xml:lang="en">Ovid</persName>  <persName xml:lang="la">Publius Ovidius Naso</persName>  <birth when="-0044-03-20"> 20 March 43 BC <placeName>    <settlement type="city">Sulmona</settlement>    <country key="IT">Italy</country>   </placeName>  </birth>  <death notBefore="0017notAfter="0018">17 or 18 AD <placeName>    <settlement type="city">Tomis (Constanta)</settlement>    <country key="RO">Romania</country>   </placeName>  </death> </person>
ExampleThe following exemplifies an adaptation of the vCard standard to indicate an unknown gender for a fictional character.
<person xml:id="arielgender="U">  <persName>Ariel</persName>  <note>Character in <title level="m">The Tempest</title>.</note> </person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
   <elementRef key="ptr"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element person
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   (
      tei_model.pLike+
    | ( tei_model.personPart | tei_model.global | tei_ptr )*
   )
}

1.213. <personGrp>

<personGrp> (personal group) describes a group of individuals treated as a single person for analytic purposes. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
rolespecifies the role of this group of participants in the interaction.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as movement, employers, relatives, or servants, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

genderspecifies the gender of the participant group.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be defined locally by a project, or they may refer to an external standard.

agespecifies the age group of the participants.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sizedescribes informally the size or approximate size of the group for example by means of a number and an indication of accuracy e.g. approx 200.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Member of
Contained by
namesdates: event listPerson org
May contain
Note

May contain a prose description organized as paragraphs, or any sequence of demographic elements in any combination.

The global xml:id attribute should be used to identify each speaking participant in a spoken text if the who attribute is specified on individual utterances.

Example
<personGrp xml:id="pg1role="audience"  sex="mixedsize="approx 50"/>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element personGrp
{
   tei_att.global.attributes,
   tei_att.sortable.attributes,
   attribute role { text }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   attribute size { list { + } }?,
   ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
}

1.214. <persona>

<persona> provides information about one of the personalities identified for a given individual, where an individual has multiple personalities. [14.3.2. The Person Element]
Modulenamesdates
Attributes
rolespecifies a primary role or classification for the persona.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as artist, employer, author, relative, or servant, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

sexspecifies the sex of the persona.
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be locally defined by a project, or may refer to an external standard.

genderspecifies the gender of the persona.
StatusOptional
Datatype1–∞ occurrences of teidata.gender separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

agespecifies an age group for the persona.
StatusOptional
Datatypeteidata.enumerated
Note

Values for this attribute may be locally defined by a project, using arbitrary keywords such as infant, child, teen, adult, or senior, each of which should be associated with a definition. Such local definitions will typically be provided by a <valList> element in the project schema specification.

Member of
Contained by
May contain
Note

Note that a persona is not the same as a role. A role may be assumed by different people on different occasions, whereas a persona is unique to a particular person, even though it may resemble others. Similarly, when an actor takes on or enacts the role of a historical person, they do not thereby acquire a new persona.

Example
<person sex="Mage="adult">  <persona sex="M">   <persName>Dr Henry Jekyll</persName>  </persona>  <persona sex="Mage="youth">   <persName>Edward Hyde</persName>  </persona> </person>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.personPart"/>
   <classRef key="model.global"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element persona
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   attribute role { list { + } }?,
   attribute sex { list { + } }?,
   attribute gender { list { + } }?,
   attribute age { text }?,
   ( tei_model.pLike+ | ( tei_model.personPart | tei_model.global )* )
}

1.215. <place>

<place> (place) contains data about a geographic location [14.3.4. Places]
Modulenamesdates
Attributes
Member of
Contained by
namesdates: event listPlace org place
May contain
Example
<place>  <country>Lithuania</country>  <country xml:lang="lt">Lietuva</country>  <place>   <settlement>Vilnius</settlement>  </place>  <place>   <settlement>Kaunas</settlement>  </place> </place>
Content model
<content>
 <sequence>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="0" maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.placeStateLike"/>
    <classRef key="model.eventLike"/>
    <elementRef key="name"/>
   </alternate>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
   <elementRef key="idno"/>
   <elementRef key="ptr"/>
   <elementRef key="linkGrp"/>
   <elementRef key="link"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.placeLike"/>
   <elementRef key="listPlace"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element place
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.editLike.attributes,
   tei_att.sortable.attributes,
   (
      tei_model.headLike*,
      (
         tei_model.pLike*
       | (
            tei_model.labelLike
          | tei_model.placeStateLike
          | tei_model.eventLike
          | tei_name
         )*
      ),
      (
         tei_model.noteLike
       | tei_model.biblLike
       | tei_idno
       | tei_ptr
       | linkGrp
       | link
      )*,
      ( tei_model.placeLike | tei_listPlace )*
   )
}

1.216. <placeName>

<placeName> (place name) contains an absolute or relative place name. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement>Rochester</settlement>  <region>New York</region> </placeName>
Example
<placeName>  <geogName>Arrochar Alps</geogName>  <region>Argylshire</region> </placeName>
Example
<placeName>  <measure>10 miles</measure>  <offset>Northeast of</offset>  <settlement>Attica</settlement> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element placeName
{
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.217. <population>

<population> (population) contains information about the population of a place. [14.3.4.3. States, Traits, and Events]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<population when="2001-04resp="#UKCensus">  <population type="white">   <desc>54153898</desc>  </population>  <population type="asian">   <desc>11811423</desc>  </population>  <population type="black">   <desc>1148738</desc>  </population>  <population type="mixed">   <desc>677117</desc>  </population>  <population type="chinese">   <desc>247403</desc>  </population>  <population type="other">   <desc>230615</desc>  </population> </population>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <alternate>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <classRef key="model.labelLike"
     minOccurs="1" maxOccurs="unbounded"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </sequence>
  <elementRef key="population"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element population
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      tei_model.headLike*,
      (
         (
            ( tei_model.pLike+ | tei_model.labelLike+ ),
            ( tei_model.noteLike | tei_model.biblLike )*
         )?
      ),
      tei_population*
   )
}

1.218. <postBox>

<postBox> (postal box or post office box) contains a number or other identifier for some postal delivery point other than a street address. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
core: address
May containCharacter data only
Note

The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

Example
<postBox>P.O. Box 280</postBox>
Example
<postBox>Postbus 532</postBox>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postBox { tei_att.global.attributes, text }

1.219. <postCode>

<postCode> (postal code) contains a numerical or alphanumeric code used as part of a postal address to simplify sorting or delivery of mail. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
core: address
May containCharacter data only
Note

The position and nature of postal codes is highly country-specific; the conventions appropriate to the country concerned should be used.

Example
<postCode>HR1 3LR</postCode>
Example
<postCode>60142-7</postCode>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element postCode { tei_att.global.attributes, text }

1.220. <postscript>

<postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<div type="letter">  <opener>   <dateline>    <placeName>Rimaone</placeName>    <date when="2006-11-21">21 Nov 06</date>   </dateline>   <salute>Dear Susan,</salute>  </opener>  <p>Thank you very much for the assistance splitting those    logs. I'm sorry about the misunderstanding as to the size of    the task. I really was not asking for help, only to borrow the    axe. Hope you had fun in any case.</p>  <closer>   <salute>Sincerely yours,</salute>   <signed>Seymour</signed>  </closer>  <postscript>   <label>P.S.</label>   <p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p>  </postscript> </div>
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.divTopPart"/>
  </alternate>
  <classRef key="model.common"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.global"/>
   <classRef key="model.common"/>
  </alternate>
  <sequence minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.divBottomPart"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element postscript
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      ( tei_model.global | tei_model.divTopPart )*,
      tei_model.common,
      ( tei_model.global | tei_model.common )*,
      ( ( tei_model.divBottomPart, tei_model.global* )* )
   )
}

1.221. <prefixDef>

<prefixDef> (prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [17.2.3. Using Abbreviated Pointers]
Moduleheader
Attributes
identsupplies a name which functions as the prefix for an abbreviated pointing scheme such as a private URI scheme. The prefix constitutes the text preceding the first colon.
StatusRequired
Datatypeteidata.prefix
Note

The value is limited to teidata.prefix so that it may be mapped directly to a URI prefix.

Contained by
May contain
core: p
Note

The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base.

Example
<prefixDef ident="ref"  matchPattern="([a-z]+)"  replacementPattern="../../references/references.xml#$1">  <p> In the context of this project, private URIs with    the prefix "ref" point to <gi>div</gi> elements in    the project's global references.xml file.  </p> </prefixDef>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element prefixDef
{
   tei_att.global.attributes,
   tei_att.patternReplacement.attributes,
   attribute ident { text },
   tei_model.pLike*
}

1.222. <principal>

<principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element principal
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.223. <profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Member of
Contained by
May contain
Note

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.

Example
<profileDesc>  <langUsage>   <language ident="fr">French</language>  </langUsage>  <textDesc n="novel">   <channel mode="w">print; part issues</channel>   <constitution type="single"/>   <derivation type="original"/>   <domain type="art"/>   <factuality type="fiction"/>   <interaction type="none"/>   <preparedness type="prepared"/>   <purpose type="entertaindegree="high"/>   <purpose type="informdegree="medium"/>  </textDesc>  <settingDesc>   <setting>    <name>Paris, France</name>    <time>Late 19th century</time>   </setting>  </settingDesc> </profileDesc>
Content model
<content>
 <classRef key="model.profileDescPart"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element profileDesc { tei_att.global.attributes, tei_model.profileDescPart* }

1.224. <projectDesc>

<projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<projectDesc>  <p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p> </projectDesc>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element projectDesc
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.225. <ptr>

<ptr> (pointer) defines a pointer to another location. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
Member of
Contained by
May containEmpty element
Example
<ptr target="#p143 #p144"/> <ptr target="http://www.tei-c.org"/> <ptr cRef="1.3.4"/>
Schematron
<sch:rule context="tei:ptr"> <sch:report test="@target and @cRef">Only one of the attributes @target and @cRef may be supplied on <sch:name/>.</sch:report> </sch:rule>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element ptr
{
   tei_att.cReferencing.attributes,
   tei_att.declaring.attributes,
   tei_att.global.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   empty
}

1.226. <pubPlace>

<pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.12.2.4. Imprint, Size of a Document, and Reprint Information]
Modulecore
Attributes
Member of
Contained by
textstructure: docImprint
May contain
Example
<publicationStmt>  <publisher>Oxford University Press</publisher>  <pubPlace>Oxford</pubPlace>  <date>1989</date> </publicationStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element pubPlace
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_macro.phraseSeq
}

1.227. <publicationStmt>

<publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Note

Where a publication statement contains several members of the model.publicationStmtPart.agency or model.publicationStmtPart.detail classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

Example
<publicationStmt>  <publisher>C. Muquardt </publisher>  <pubPlace>Bruxelles &amp; Leipzig</pubPlace>  <date when="1846"/> </publicationStmt>
Example
<publicationStmt>  <publisher>Chadwyck Healey</publisher>  <pubPlace>Cambridge</pubPlace>  <availability>   <p>Available under licence only</p>  </availability>  <date when="1992">1992</date> </publicationStmt>
Example
<publicationStmt>  <publisher>Zea Books</publisher>  <pubPlace>Lincoln, NE</pubPlace>  <date>2017</date>  <availability>   <p>This is an open access work licensed under a Creative Commons Attribution 4.0 International license.</p>  </availability>  <ptr target="http://digitalcommons.unl.edu/zeabook/55"/> </publicationStmt>
Content model
<content>
 <alternate>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.publicationStmtPart.agency"/>
   <classRef key="model.publicationStmtPart.detail"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element publicationStmt
{
   tei_att.global.attributes,
   (
      (
         (
            tei_model.publicationStmtPart.agency,
            tei_model.publicationStmtPart.detail*
         )+
      )
    | tei_model.pLike+
   )
}

1.228. <publisher>

<publisher> (publisher) provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.]
Modulecore
Attributes
Member of
Contained by
textstructure: docImprint
May contain
Note

Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page

Example
<imprint>  <pubPlace>Oxford</pubPlace>  <publisher>Clarendon Press</publisher>  <date>1987</date> </imprint>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element publisher
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_macro.phraseSeq
}

1.229. <punctuation>

<punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation]
Moduleheader
Attributes
marksindicates whether or not punctation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no punctuation marks have been retained
some
some punctuation marks have been retained
all
all punctuation marks have been retained
placementindicates the positioning of punctuation marks that are associated with marked up text as being encoded within the element surrounding the text or immediately before or after it.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
internal
punctuation marks found at the start or end of a marked up text component are included within its surrounding element;
external
punctuation marks found at the start or end of a marked up text component appear immediately before or after the surrounding element
Member of
Contained by
May contain
core: p
Example
<punctuation marks="all"  placement="internal">  <p>All punctuation marks in the source text have been retained and represented using the    appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey    the same information (for example, a sentence ends with a question mark and is also tagged    as <gi>s</gi>) the punctuation mark is captured as content within the element.</p> </punctuation>
ExampleExternal placement of punctuation:
<p>I would agree with Saint Augustine that “<quote>An unjust law is no law at all</quote>.”</p>
ExampleInternal placement of punctuation:
<p>I would agree with Saint Augustine that <quote>“An unjust law is no law at all.”</quote> </p>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element punctuation
{
   tei_att.declarable.attributes,
   tei_att.global.attributes,
   attribute marks { "none" | "some" | "all" }?,
   attribute placement { "internal" | "external" }?,
   tei_model.pLike*
}

1.230. <q>

<q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation]
Modulecore
Attributes
type(type) may be used to indicate whether the offset passage is spoken or thought, or to characterize it more finely.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
spoken
(spoken) representation of speech
thought
(thought) representation of thought, e.g. internal monologue
written
(written) quotation from a written source
soCalled
(so called) authorial distance
foreign
(foreign) foreign words
distinct
(distinct) linguistically distinct
term
technical term
emph
(emph) rhetorically emphasized
mentioned
(mentioned) refering to itself, not its normal referent
Member of
Contained by
May contain
Note

May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks.

Example
It is spelled <q>Tübingen</q> — to enter the letter <q>u</q> with an umlaut hold down the <q>option</q> key and press <q>0 0 f c</q>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element q
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute type
   {
      "spoken"
    | "thought"
    | "written"
    | "soCalled"
    | "foreign"
    | "distinct"
    | "term"
    | "emph"
    | "mentioned"
   }?,
   tei_macro.specialPara
}

1.231. <quotation>

<quotation> (quotation) specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
marks(quotation marks) indicates whether or not quotation marks have been retained as content within the text.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
none
no quotation marks have been retained
some
some quotation marks have been retained
all
all quotation marks have been retained
Member of
Contained by
May contain
core: p
Example
<quotation marks="none">  <p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the  <gi>q</gi> element is used to specify what kinds of quotation mark was used, according    to the following list: <list type="gloss">    <label>dq</label>    <item>double quotes, open and close</item>    <label>sq</label>    <item>single quotes, open and close</item>    <label>dash</label>    <item>long dash open, no close</item>    <label>dg</label>    <item>double guillemets, open and close</item>   </list>  </p> </quotation>
Example
<quotation marks="all">  <p>All quotation marks are retained in the text and are represented by appropriate Unicode    characters.</p> </quotation>
Schematron
<sch:rule context="tei:quotation"> <sch:report test="not( @marks ) and not( tei:p )"> On <sch:name/>, either the @marks attribute should be used, or a paragraph of description provided </sch:report> </sch:rule>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element quotation
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   attribute marks { "none" | "some" | "all" }?,
   tei_model.pLike*
}

1.232. <quote>

<quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts]
Modulecore
Attributes
Member of
Contained by
May contain
Note

If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element.

Example
Lexicography has shown little sign of being affected by the work of followers of J.R. Firth, probably best summarized in his slogan, <quote>You shall know a word by the company it keeps</quote> <ref>(Firth, 1957)</ref>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element quote
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.notated.attributes,
   tei_att.cmc.attributes,
   tei_macro.specialPara
}

1.233. <rb>

<rb> (ruby base) contains the base text annotated by a ruby gloss. [3.4.2. Ruby Annotations]
Modulecore
Attributes
Contained by
core: ruby
May contain
ExampleThe word 你 好 nǐ hǎo (hello) is glossed in pinyin to provide a pronunciation guide.
<p xml:lang="zh"> <!--...-->  <ruby>   <rb></rb>   <rt place="above"></rt>  </ruby>  <ruby>   <rb></rb>   <rt place="above">hǎo</rt>  </ruby> <!--...--> </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rb
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_macro.phraseSeq
}

1.234. <ref>

<ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.7. Simple Links and Cross-References 17.1. Links]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The target and cRef attributes are mutually exclusive.

Example
See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second sentence</ref>
Example
See also <ref target="#locution">s.v. <term>locution</term> </ref>.
Schematron
<sch:rule context="tei:ref"> <sch:report test="@target and @cRef">Only one of the attributes @target' and @cRef' may be supplied on <sch:name/> </sch:report> </sch:rule>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element ref
{
   tei_att.cReferencing.attributes,
   tei_att.declaring.attributes,
   tei_att.global.attributes,
   tei_att.internetMedia.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.235. <refState>

<refState> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Moduleheader
Attributes
lengthspecifies the fixed length of the reference component.
StatusOptional
Datatypeteidata.count
Note

When constructing a reference, if the reference component found is of numeric type, the length is made up by inserting leading zeros; if it is not, by inserting trailing blanks. In either case, reference components are truncated if necessary at the right hand side.

When seeking a reference, the length indicates the number of characters which should be compared. Values longer than this will be regarded as matching, if they start correctly. If no value is provided, the length is unlimited and goes to the next delimiter or to the end of the value.

delim(delimiter) supplies a delimiting string following the reference component.
StatusOptional
Datatypeteidata.text
Contained by
header: refsDecl
May containEmpty element
Example
<refState unit="bookdelim=":"/> <refState unit="linelength="4"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element refState
{
   tei_att.global.attributes,
   tei_att.milestoneUnit.attributes,
   tei_att.edition.attributes,
   attribute length { text }?,
   attribute delim { text }?,
   empty
}

1.236. <refsDecl>

<refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
Example
<refsDecl>  <cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"   replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/> </refsDecl>
This example is a formal representation for the referencing scheme described informally in the following example.
Example
<refsDecl>  <p>References are made up by concatenating the value for the  <att>n</att> attribute on the highest level <gi>div</gi>    element, followed by a space, followed by the sequential    number of the next level <gi>div</gi> followed by a colon    followed by the sequential number of the next (and lowest)    level <gi>div</gi>.</p> </refsDecl>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="citeStructure"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="cRefPattern"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="refState" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element refsDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_model.pLike+ | tei_citeStructure+ | tei_cRefPattern+ | tei_refState+ )
}

1.237. <reg>

<reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.5.2. Regularization and Normalization 13. Critical Apparatus]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleIf all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone:
<q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg> </q>
ExampleIt is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings:
<q>Please <choice>   <reg resp="#LB">knock</reg>   <orig>cnk</orig>  </choice> if an <choice>   <reg>answer</reg>   <orig>nsr</orig>  </choice> is <choice>   <reg>required</reg>   <orig>reqd</orig>  </choice> </q>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element reg
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.238. <region>

<region> (region) contains the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <region type="staten="IL">Illinois</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element region
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.239. <relatedItem>

<relatedItem> contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. [3.12.2.7. Related Items]
Modulecore
Attributes
targetpoints to the related bibliographic element by means of an absolute or relative URI reference
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Note

If the target attribute is used to reference the related bibliographic item, the element must be empty.

Example
<biblStruct>  <monogr>   <author>Shirley, James</author>   <title type="main">The gentlemen of Venice</title>   <imprint>    <pubPlace>New York</pubPlace>    <publisher>Readex Microprint</publisher>    <date>1953</date>   </imprint>   <extent>1 microprint card, 23 x 15 cm.</extent>  </monogr>  <series>   <title>Three centuries of drama: English, 1642–1700</title>  </series>  <relatedItem type="otherForm">   <biblStruct>    <monogr>     <author>Shirley, James</author>     <title type="main">The gentlemen of Venice</title>     <title type="sub">a tragi-comedie presented at the private house in Salisbury          Court by Her Majesties servants</title>     <imprint>      <pubPlace>London</pubPlace>      <publisher>H. Moseley</publisher>      <date>1655</date>     </imprint>     <extent>78 p.</extent>    </monogr>   </biblStruct>  </relatedItem> </biblStruct>
Schematron
<sch:rule context="tei:relatedItem"> <sch:report test="@target and count( child::* ) > 0">If the @target attribute on <sch:name/> is used, the relatedItem element must be empty</sch:report> <sch:assert test="@target or child::*">A relatedItem element should have either a @target attribute or a child element to indicate the related bibliographic item</sch:assert> </sch:rule>
Content model
<content>
 <alternate minOccurs="0">
  <classRef key="model.biblLike"/>
  <classRef key="model.ptrLike"/>
 </alternate>
</content>
    
Schema Declaration
element relatedItem
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute target { text }?,
   ( tei_model.biblLike | tei_model.ptrLike )?
}

1.240. <relation>

<relation> (relationship) describes any kind of relationship or linkage amongst a specified group of places, events, persons, objects or other items. [14.3.2.3. Personal Relationships]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
namesupplies a name for the kind of relationship of which this is an instance.
StatusOptional
Datatypeteidata.enumerated
activeidentifies the ‘active’ participants in a non-mutual relationship, or all the participants in a mutual one.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mutualsupplies a list of participants amongst all of whom the relationship holds equally.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
passiveidentifies the ‘passive’ participants in a non-mutual relationship.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Contained by
May contain
core: desc
Note

Only one of the attributes active and mutual may be supplied; the attribute passive may be supplied only if the attribute active is supplied. Not all of these constraints can be enforced in all schema languages.

Example
<relation type="socialname="supervisor"  active="#p1passive="#p2 #p3 #p4"/>
This indicates that the person with identifier p1 is supervisor of persons p2, p3, and p4.
Example
<relation type="personalname="friends"  mutual="#p2 #p3 #p4"/>
This indicates that p2, p3, and p4 are all friends.
Example
<relation type="CRM"  name="P89_falls_within"  active="http://id.clarosnet.org/places/metamorphoses/place/italy-orvieto"  passive="http://id.clarosnet.org/places/metamorphoses/country/IT"/>
This indicates that there is a relation, defined by CIDOC CRM, between two resources identified by URLs.
Example
<relation resp="http://viaf.org/viaf/44335536/"  ref="http://purl.org/saws/ontology#isVariantOf"  active="http://www.ancientwisdoms.ac.uk/cts/urn:cts:greekLit:tlg3017.Syno298.sawsGrc01:divedition.divsection1.o14.a107"  passive="http://data.perseus.org/citations/urn:cts:greekLit:tlg0031.tlg002.perseus-grc1:9.35"/>
This example records a relationship, defined by the SAWS ontology, between a passage of text identified by a CTS URN, and a variant passage of text in the Perseus Digital Library, and assigns the identification of the relationship to a particular editor (all using resolvable URIs).
Schematron
<sch:rule context="tei:relation"> <sch:assert test="@ref or @key or @name">One of the attributes @name, @ref or @key must be supplied</sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@active and @mutual">Only one of the attributes @active and @mutual may be supplied</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:relation"> <sch:report test="@passive and not(@active)">the attribute @passive may be supplied only if the attribute @active is supplied</sch:report> </sch:rule>
Content model
<content>
 <elementRef key="desc" minOccurs="0"/>
</content>
    
Schema Declaration
element relation
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.canonical.attributes,
   tei_att.sortable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute name { text }?,
   ( attribute active { list { + } }? | attribute mutual { list { + } }? ),
   attribute passive { list { + } }?,
   tei_desc?
}

1.241. <remarks>

<remarks> (remarks) contains any commentary or discussion about the usage of an element, attribute, class, or entity not otherwise documented within the containing element. [23.5. Element Specifications 23.5.3. Attribute List Specification 23.6. Class Specifications 23.7. Macro Specifications]
Moduletagdocs
Attributes
identspecifies the remark concerned.
StatusOptional
Datatypeteidata.text
Contained by
May contain
core: p
Note

Contains at least one paragraph, unless it is empty.

As defined in ODD, must contain paragraphs; should be special.para

Example
<remarks>  <p>This element is probably redundant.</p> </remarks>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element remarks
{
   tei_att.global.attributes,
   tei_att.combinable.attributes,
   tei_att.translatable.attributes,
   attribute ident { text }?,
   tei_model.pLike+
}

1.242. <rendition>

<rendition> (rendition) supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
scopewhere CSS is used, provides a way of defining ‘pseudo-elements’, that is, styling rules applicable to specific sub-portions of an element.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
first-line
styling applies to the first line of the target element
first-letter
styling applies to the first letter of the target element
before
styling should be applied immediately before the content of the target element
after
styling should be applied immediately after the content of the target element
selectorcontains a selector or series of selectors specifying the elements to which the contained style description applies, expressed in the language specified in the scheme attribute.
StatusOptional
Datatypeteidata.text
<rendition scheme="css"  selector="text, front, back, body, div, p, ab"> display: block; </rendition>
<rendition scheme="css"  selector="*[rend*=italic]"> font-style: italic; </rendition>
Note

Since the default value of the scheme attribute is assumed to be CSS, the default expectation for this attribute, in the absence of scheme, is that CSS selector syntax will be used.

While rendition is used to point from an element in the transcribed source to a <rendition> element in the header which describes how it appears, the selector attribute allows the encoder to point in the other direction: from a <rendition> in the header to a collection of elements which all share the same renditional features. In both cases, the intention is to record the appearance of the source text, not to prescribe any particular output rendering.

Contained by
header: tagsDecl
May contain
Example
<tagsDecl>  <rendition xml:id="r-centerscheme="css">text-align: center;</rendition>  <rendition xml:id="r-smallscheme="css">font-size: small;</rendition>  <rendition xml:id="r-largescheme="css">font-size: large;</rendition>  <rendition xml:id="initcaps"   scope="first-letterscheme="css">font-size: xx-large</rendition> </tagsDecl>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element rendition
{
   tei_att.global.attributes,
   tei_att.styleDef.attributes,
   attribute scope { text }?,
   attribute selector { text }?,
   tei_macro.limitedContent
}

1.243. <residence>

<residence> (residence) describes a person's present or past places of residence. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
primary
secondary
temporary
permanent
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<residence>Childhood in East Africa and long term resident of Glasgow, Scotland.</residence>
Example
<residence notAfter="1997">Mbeni estate, Dzukumura region, Matabele land</residence> <residence notBefore="1903notAfter="1996">  <placeName>   <settlement>Glasgow</settlement>   <region>Scotland</region>  </placeName> </residence>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element residence
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.244. <resp>

<resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
core: respStmt
May contain
Note

The attribute ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form by referring directly to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage.

Example
<respStmt>  <resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>  <name>Edward Child</name> </respStmt>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element resp
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.245. <respStmt>

<respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement]
Modulecore
Attributes
Member of
Contained by
May contain
core: name note resp
namesdates: orgName persName
Example
<respStmt>  <resp>transcribed from original ms</resp>  <persName>Claus Huitfeldt</persName> </respStmt>
Example
<respStmt>  <resp>converted to XML encoding</resp>  <name>Alan Morrison</name> </respStmt>
Content model
<content>
 <sequence>
  <alternate>
   <sequence>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
   </sequence>
   <sequence>
    <classRef key="model.nameLike.agent"
     minOccurs="1" maxOccurs="unbounded"/>
    <elementRef key="resp" minOccurs="1"
     maxOccurs="unbounded"/>
   </sequence>
  </alternate>
  <elementRef key="note" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element respStmt
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   (
      (
         ( tei_resp+, tei_model.nameLike.agent+ )
       | ( tei_model.nameLike.agent+, tei_resp+ )
      ),
      tei_note*
   )
}

1.246. <revisionDesc>

<revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components]
Moduleheader
Attributes
Contained by
header: teiHeader
May contain
core: list
Note

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally <change> elements should be given in reverse date order, with the most recent change at the start of the list.

Example
<revisionDesc status="embargoed">  <change when="1991-11-11who="#LB"> deleted chapter 10 </change> </revisionDesc>
Content model
<content>
 <alternate>
  <elementRef key="list" minOccurs="1"
   maxOccurs="unbounded"/>
  <elementRef key="listChange"
   minOccurs="1" maxOccurs="unbounded"/>
  <elementRef key="change" minOccurs="1"
   maxOccurs="unbounded"/>
 </alternate>
</content>
    
Schema Declaration
element revisionDesc
{
   tei_att.global.attributes,
   tei_att.docStatus.attributes,
   ( tei_list+ | tei_listChange+ | tei_change+ )
}

1.247. <roleName>

<roleName> (role name) contains a name component which indicates that the referent has a particular role or position in society, such as an official title or rank. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Note

A <roleName> may be distinguished from an <addName> by virtue of the fact that, like a title, it typically exists independently of its holder.

Example
<persName>  <forename>William</forename>  <surname>Poulteny</surname>  <roleName>Earl of Bath</roleName> </persName>
Example
<p>The <roleName role="solicitor_general">S.G.</roleName> is the only national public official, including the Supreme Court justices, required by statute to be “learned in the law.”</p>
Example
<p>  <persName ref="#NJF">   <roleName role="solicitor_general">Solicitor General</roleName> Noel J. Francisco</persName>, representing the administration, asserted in rebuttal that there was nothing to disavow (...) <persName ref="#NJF">Francisco</persName> had violated the scrupulous standard of candor about the facts and the law that <roleName role="solicitor_general">S.G.s</roleName>, in Republican and Democratic administrations alike, have repeatedly said they must honor. </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element roleName
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.248. <rs>

<rs> (referencing string) contains a general purpose name or referring string. [14.2.1. Personal Names 3.6.1. Referring Strings]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs> to him one day, <q>have you heard that <rs type="place">Netherfield Park</rs> is let at last?</q>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rs
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.249. <rt>

<rt> (ruby text) contains a ruby text, an annotation closely associated with a passage of the main text. [3.4.2. Ruby Annotations]
Modulecore
Attributes
targetsupplies a pointer to the base being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce that either target or both from and to (or none) are used, but not target in combination with either from or to.
<sch:rule context="tei:rt/@target"> <sch:report test="../@from | ../@to">When target= is present, neither from= nor to= should be.</sch:report> </sch:rule>
Note

Should point to a single <rb> or an element that is inside an <rb>. To refer to multiple elements or text nodes at once use from and to.

frompoints to the starting point of the span of text being glossed by this ruby text.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of to iff there is a from.
<sch:rule context="tei:rt/@from"> <sch:assert test="../@to">When from= is present, the to= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
topoints to the ending point of the span of text being glossed.
StatusOptional
Datatypeteidata.pointer
SchematronEnforce the presence of from iff there is a to.
<sch:rule context="tei:rt/@to"> <sch:assert test="../@from">When to= is present, the from= attribute of <sch:name/> is required.</sch:assert> </sch:rule>
Contained by
core: ruby
May contain
Note

Where the place attribute is not provided on the <rt> element, the default assumption is that the ruby gloss is above where the text is horizontal, and to the right of the text where it is vertical.

ExampleThe word 大統領 daitōryō (president) is glossed character by character in hiragana to provide a pronunciation guide.
<p style="writing-mode: vertical-rl"  xml:lang="ja"> <!--...-->  <ruby>   <rb></rb>   <rt place="right">だい</rt>  </ruby>  <ruby>   <rb></rb>   <rt place="right">とう</rt>  </ruby>  <ruby>   <rb></rb>   <rt place="right">りょう</rt>  </ruby> <!--...--> </p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element rt
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.transcriptional.attributes,
   attribute target { text }?,
   attribute from { text }?,
   attribute to { text }?,
   tei_macro.phraseSeq
}

1.250. <ruby>

<ruby> (ruby container) contains a passage of base text along with its associated ruby gloss(es). [3.4.2. Ruby Annotations]
Modulecore
Attributes
Member of
Contained by
May contain
core: rb rt
ExampleThe word 入学試験 nyūgakushiken (university entrance exam) is glossed with a hiragana phonation guide.
<p xml:lang="ja"> <!--...-->  <ruby>   <rb>入学試験</rb>   <rt place="above">にゅうがくしけん</rt>  </ruby> <!--...--> </p>
ExampleThis fictional example shows the initialism TEI glossed letter-by-letter with an IPA transcription.
<ruby>  <rb>T</rb>  <rt>ti:</rt> </ruby> <ruby>  <rb>E</rb>  <rt>i:</rt> </ruby> <ruby>  <rb>I</rb>  <rt></rt> </ruby>
Content model
<content>
 <sequence>
  <elementRef key="rb" minOccurs="1"
   maxOccurs="1"/>
  <elementRef key="rt" minOccurs="1"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element ruby
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   ( tei_rb, tei_rt+ )
}

1.251. <said>

<said> (speech or thought) indicates passages thought or spoken aloud, whether explicitly indicated in the source or not, whether directly or indirectly reported, whether by real people or fictional characters. [3.3.3. Quotation]
Modulecore
Attributes
aloudmay be used to indicate whether the quoted matter is regarded as having been vocalized or signed.
StatusOptional
Datatypeteidata.xTruthValue
<p> Celia thought privately, <said aloud="false">Dorothea quite despises Sir James Chettam;    I believe she would not accept him.</said> Celia felt that this was a pity. <!-- ... --> </p>
Note

The value true indicates the encoded passage was expressed outwardly (whether spoken, signed, sung, screamed, chanted, etc.); the value false indicates that the encoded passage was thought, but not outwardly expressed.

directmay be used to indicate whether the quoted matter is regarded as direct or indirect speech.
StatusOptional
Datatypeteidata.xTruthValue
Defaulttrue
<!-- in the header --><editorialDecl>  <quotation marks="none"/> </editorialDecl> <!-- ... --> <p>Tantripp had brought a card, and said that <said direct="false">there was a gentleman waiting in the lobby</said>. The courier had told him that <said direct="false">only Mrs. Casaubon was at home</said>, but he said <said direct="false">he was a relation of Mr. Casaubon's: would she see him?</said> </p>
Note

The value true indicates the speech or thought is represented directly; the value false that speech or thought is represented indirectly, e.g. by use of a marked verbal aspect.

Member of
Contained by
May contain
Example
<!-- in the header --><editorialDecl>  <quotation marks="all"/> </editorialDecl> <!-- ... --> <p>  <said>"Our minstrel here will warm the old man's heart with song, dazzle him with jewels and    gold"</said>, a troublemaker simpered. <said>"He'll trample on the Duke's camellias, spill    his wine, and blunt his sword, and say his name begins with X, and in the end the Duke    will say, <said>'Take Saralinda, with my blessing, O lordly Prince of Rags and Tags, O      rider of the sun!'</said>"</said> </p>
Example
<p>  <said aloud="truerend="pre(“) post(”)">Hmmm</said>, said a small voice in his ear. <said aloud="truerend="pre(“) post(”)">Difficult. Very difficult. Plenty of courage, I see.    Not a bad mind either. there's talent, oh my goodness, yes — and a nice thirst to prove    yourself, now that's interesting. … So where shall I put you?</said> </p> <p>Harry gripped the edges of the stool and thought, <said aloud="falserend="italic">Not    Slytherin, not Slytherin</said>.</p>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element said
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   tei_att.cmc.attributes,
   attribute aloud { text }?,
   attribute direct { text }?,
   tei_macro.specialPara
}

1.252. <salute>

<salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<salute>To all courteous mindes, that will voutchsafe the readinge.</salute>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element salute
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.253. <samplingDecl>

<samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Note

This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest.

Example
<samplingDecl>  <p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each    text identified as relevant by respondents.</p> </samplingDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element samplingDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.254. <schemaRef>

<schemaRef> (schema reference) describes or points to a related customization or schema file [2.3.10. The Schema Specification]
Moduleheader
Attributes
keythe identifier used for the customization or schema
StatusOptional
Datatypeteidata.xmlName
Member of
Contained by
header: encodingDesc
May contain
core: desc
Example
<schemaRef type="interchangeODD"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.odd"/> <schemaRef type="interchangeRNG"  url="http://www.tei-c.org/release/xml/tei/custom/odd/tei_lite.rng"/> <schemaRef type="projectODD"  url="file:///schema/project.odd"/>
Content model
<content>
 <classRef key="model.descLike"
  minOccurs="0"/>
</content>
    
Schema Declaration
element schemaRef
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.resourced.attributes,
   attribute key { text }?,
   tei_model.descLike?
}

1.255. <schemaSpec>

<schemaSpec> (schema specification) generates a TEI-conformant schema and documentation for it. [2.3. The Encoding Description 23.2. Modules and Schemas 24.5.1. Making a Unified ODD]
Moduletagdocs
Attributes
startspecifies entry points to the schema, i.e. which patterns may be used as the root of documents conforming to it.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
DefaultTEI
prefixspecifies a default prefix which will be prepended to all patterns relating to TEI elements, unless otherwise stated.
StatusOptional
Datatype0–1 occurrences of teidata.xmlName separated by whitespace
Note

Use of this attribute allows an external schema which has an element with the same local name as a TEI element to be mixed in.

targetLang(target language) specifies which language to use when creating the objects in a schema if names for elements or attributes are available in more than one language
StatusOptional
Datatypeteidata.language
docLang(documentation language) specifies which languages to use when creating documentation if the description for an element, attribute, class or macro is available in more than one language
StatusOptional
Datatype1–∞ occurrences of teidata.language separated by whitespace
Note

Although multiple languages may be specified, the current TEI ODD processor is only capable of handling one.

defaultExceptions(default namespace exclusions) provides a list of namespaces and/or prefixed element names to be excluded by default from anyName in RELAX NG schemas
StatusRecommended
Datatype1–∞ occurrences of teidata.namespaceOrName separated by whitespace
Defaulthttp://www.tei-c.org/ns/1.0 teix:egXML
Note

Specifies defaults for the except attribute of <anyElement>. RELAX NG validation (unless DTD Compatibility Mode is turned off) requires that any elements which may take an xml:id be excluded from the content of anyName name classes. For normal TEI purposes, this includes anything in the TEI namespace and the <egXML> element. The defaultExceptions attribute sets the global defaults for these exclusions. Element prefixes must be declared using a namespace declaration on the parent or an ancestor element.

Member of
Contained by
May contain
Note

A <schemaSpec> combines references to modules, individual element or macro declarations, and specification groups together to form a unified schema.

The processing of the <schemaSpec> element must resolve any conflicts amongst the declarations it either contains or refers to. Different ODD processors may generate schemas and documentation using different concrete syntaxes.

The source may be specified (on the source attribute) in the form of a private URI, for which the recommended format is tei:x.y.z, where x.y.z indicates the version number, e.g. tei:1.5.1 for 1.5.1 release of TEI P5 or (as a special case) tei:current for whatever is the latest release. The source indicated must provide a set of TEI-conformant specifications in a form directly usable by an ODD processor. By default, this will be the location of the current release of the TEI Guidelines.

Example
<schemaSpec prefix="TEI_ident="testsvg"  start="TEI svg">  <moduleRef source="tei:current"   key="header"/>  <moduleRef key="core"/>  <moduleRef key="drama"/>  <moduleRef url="svg11.rng"/> </schemaSpec>
This schema combines elements from the current versions of the drama and core modules, the current release version of the header module, and elements from an existing RELAX NG schema available from the URL indicated.
Example
<schemaSpec ident="Bare-plus"  source="tei_bare.compiled.oddstart="TEI">  <moduleRef key="tei"/>  <moduleRef key="header"/>  <elementRef key="qsource="tei:3.0.0"/>  <moduleRef key="textstructure"/> </schemaSpec>
This schema starts with a pre-existing customization of the TEI called TEI Bare (a customization with a minimal selection of elements). The <q> element is not available in TEI Bare, but it can be brought back. In this case, we will get the version defined in TEI P5 release 3.0.0
Content model
<content>
 <sequence>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.identEquiv"/>
   <classRef key="model.descLike"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.oddRef"/>
   <classRef key="model.oddDecl"/>
   <elementRef key="listRef"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element schemaSpec
{
   tei_att.global.attributes,
   tei_att.identified.attributes,
   tei_att.namespaceable.attributes,
   tei_att.docStatus.attributes,
   attribute start { list { + } }?,
   attribute prefix { ? }?,
   attribute targetLang { text }?,
   attribute docLang { list { + } }?,
   attribute defaultExceptions { list { + } }?,
   (
      ( tei_model.identEquiv | tei_model.descLike )*,
      ( tei_model.oddRef | tei_model.oddDecl | tei_listRef )*
   )
}

1.256. <scriptNote>

<scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [11.7.2. Writing, Decoration, and Other Notations]
Moduleheader
Attributes
Contained by
May contain
Example
<scriptNote scope="sole"/>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element scriptNote
{
   tei_att.global.attributes,
   tei_att.handFeatures.attributes,
   tei_macro.specialPara
}

1.257. <segmentation>

<segmentation> (segmentation) describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<segmentation>  <p>   <gi>s</gi> elements mark orthographic sentences and are numbered sequentially within    their parent <gi>div</gi> element </p> </segmentation>
Example
<p>  <gi>seg</gi> elements are used to mark functional constituents of various types within each <gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus header <gi>classDecl</gi> </p>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element segmentation
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.258. <sequence>

<sequence> indicates that the constructs referenced by its children form a sequence [23.5.1. Defining Content Models]
Moduletagdocs
Attributes
preserveOrderif false, indicates that component elements of a sequence may occur in any order.
StatusOptional
Datatypeteidata.truthValue
Member of
Contained by
May contain
Example
<content>  <sequence>   <alternate>    <elementRef key="name"/>    <elementRef key="persName"/>   </alternate>   <elementRef key="placeNameminOccurs="0"    maxOccurs="5"/>  </sequence> </content>
This example content model matches a sequence consisting of either a <name> or a <persName> followed by nothing, or by a sequence of up to five <placeName> elements.
Schematron
<sch:rule context="tei:sequence"> <sch:assert test="count(*) gt 1">The sequence element must have at least two child elements</sch:assert> </sch:rule>
Content model
<content>
 <classRef key="model.contentPart"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element sequence
{
   tei_att.global.attributes,
   tei_att.repeatable.attributes,
   attribute preserveOrder { text }?,
   tei_model.contentPart+
}

1.259. <series>

<series> (series information) contains information about the series in which a book or other bibliographic item has appeared. [3.12.2.1. Analytic, Monographic, and Series Levels]
Modulecore
Attributes
Member of
Contained by
May contain
Example
<series xml:lang="de">  <title level="s">Halbgraue Reihe zur Historischen Fachinformatik</title>  <respStmt>   <resp>Herausgegeben von</resp>   <name type="person">Manfred Thaller</name>   <name type="org">Max-Planck-Institut für Geschichte</name>  </respStmt>  <title level="s">Serie A: Historische Quellenkunden</title>  <biblScope>Band 11</biblScope> </series>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <elementRef key="title"/>
  <classRef key="model.ptrLike"/>
  <elementRef key="editor"/>
  <elementRef key="respStmt"/>
  <elementRef key="biblScope"/>
  <elementRef key="idno"/>
  <elementRef key="textLang"/>
  <classRef key="model.global"/>
  <elementRef key="availability"/>
 </alternate>
</content>
    
Schema Declaration
element series
{
   tei_att.global.attributes,
   (
      text
    | tei_model.gLike
    | tei_title
    | tei_model.ptrLike
    | tei_editor
    | tei_respStmt
    | tei_biblScope
    | tei_idno
    | tei_textLang
    | tei_model.global
    | tei_availability
   )*
}

1.260. <seriesStmt>

<seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Example
<seriesStmt>  <title>Machine-Readable Texts for the Study of Indian Literature</title>  <respStmt>   <resp>ed. by</resp>   <name>Jan Gonda</name>  </respStmt>  <biblScope unit="volume">1.2</biblScope>  <idno type="ISSN">0 345 6789</idno> </seriesStmt>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <sequence>
   <elementRef key="title" minOccurs="1"
    maxOccurs="unbounded"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="editor"/>
    <elementRef key="respStmt"/>
   </alternate>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="idno"/>
    <elementRef key="biblScope"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element seriesStmt
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   (
      tei_model.pLike+
    | (
         tei_title+,
         ( tei_editor | tei_respStmt )*,
         ( tei_idno | tei_biblScope )*
      )
   )
}

1.261. <settlement>

<settlement> (settlement) contains the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit. [14.2.3. Place Names]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<placeName>  <settlement type="town">Glasgow</settlement>  <region>Scotland</region> </placeName>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element settlement
{
   tei_att.global.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq
}

1.262. <sex>

<sex> (sex) specifies the sex of an organism. [14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
valuesupplies a coded value for sex
StatusOptional
Datatype1–∞ occurrences of teidata.sex separated by whitespace
Note

Values for this attribute may be locally defined by a project, or they may refer to an external standard.

Member of
Contained by
May contain
Note

As with other culturally-constructed traits such as age and gender, the way in which this concept is described in different cultural contexts varies. The normalizing attributes are provided only as an optional means of simplifying that variety for purposes of interoperability or project-internal taxonomies for consistency, and should not be used where that is inappropriate or unhelpful. The content of the element may be used to describe the intended concept in more detail.

Example
<sex value="F">female</sex>
Example
<sex value="I">Intersex</sex>
Example
<sex value="TG F">Female (TransWoman)</sex>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element sex
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.datable.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   attribute value { list { + } }?,
   tei_macro.phraseSeq
}

1.263. <sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.5.1. Apparent Errors]
Modulecore
Attributes
Member of
Contained by
May contain
Example
for his nose was as sharp as a pen, and <sic>a Table</sic> of green fields.
ExampleIf all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone:
I don't know, Juan. It's so far in the past now — how <sic>we can</sic> prove or disprove anyone's theories?
ExampleIt is also possible, using the <choice> and <corr> elements, to provide a corrected reading:
I don't know, Juan. It's so far in the past now — how <choice>  <sic>we can</sic>  <corr>can we</corr> </choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as a pen, and <choice>  <sic>a Table</sic>  <corr>a' babbld</corr> </choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element sic
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.264. <signed>

<signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<signed>Thine to command <name>Humph. Moseley</name> </signed>
Example
<closer>  <signed>Sign'd and Seal'd,  <list>    <item>John Bull,</item>    <item>Nic. Frog.</item>   </list>  </signed> </closer>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element signed
{
   tei_att.global.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   tei_macro.paraContent
}

1.265. <soCalled>

<soCalled> (so called) contains a word or phrase for which the author or narrator indicates a disclaiming of responsibility, for example by the use of scare quotes or italics. [3.3.3. Quotation]
Modulecore
Attributes
Member of
Contained by
May contain
Example
To edge his way along the crowded paths of life, warning all human sympathy to keep its distance, was what the knowing ones call <soCalled>nuts</soCalled> to Scrooge.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element soCalled
{
   tei_att.global.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.266. <socecStatus>

<socecStatus> (socio-economic status) contains an informal description of a person's perceived social or economic status. [16.2.2. The Participant Description]
Modulenamesdates
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
atBirth
atDeath
dependent
inherited
independent
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
schemeidentifies the classification system or taxonomy in use, for example by pointing to a locally-defined <taxonomy> element or by supplying a URI for an externally-defined system.
StatusOptional
Datatypeteidata.pointer
codeidentifies a status code defined within the classification system or taxonomy defined by the scheme attribute.
StatusOptional
Datatypeteidata.pointer
Member of
Contained by
May contain
Note

The content of this element may be used as an alternative to the more formal specification made possible by its attributes; it may also be used to supplement the formal specification with commentary or clarification.

Example
<socecStatus scheme="#rgcode="#ab1"/>
Example
<socecStatus>Status AB1 in the RG Classification scheme</socecStatus>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element socecStatus
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute scheme { text }?,
   attribute code { text }?,
   tei_macro.phraseSeq
}

1.267. <sourceDesc>

<sourceDesc> (source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as ‘born digital’ for a text which has no previous existence. [2.2.7. The Source Description]
Moduleheader
Attributes
Contained by
May contain
Example
<sourceDesc>  <bibl>   <title level="a">The Interesting story of the Children in the Wood</title>. In  <author>Victor E Neuberg</author>, <title>The Penny Histories</title>.  <publisher>OUP</publisher>   <date>1968</date>. </bibl> </sourceDesc>
Example
<sourceDesc>  <p>Born digital: no previous source exists.</p> </sourceDesc>
Content model
<content>
 <alternate>
  <classRef key="model.pLike" minOccurs="1"
   maxOccurs="unbounded"/>
  <alternate minOccurs="1"
   maxOccurs="unbounded">
   <classRef key="model.biblLike"/>
   <classRef key="model.sourceDescPart"/>
   <classRef key="model.listLike"/>
  </alternate>
 </alternate>
</content>
    
Schema Declaration
element sourceDesc
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   (
      tei_model.pLike+
    | ( tei_model.biblLike | tei_model.sourceDescPart | tei_model.listLike )+
   )
}

1.268. <sp>

<sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.2. Speeches and Speakers]
Modulecore
Attributes
Member of
Contained by
May contain
Note

The who attribute on this element may be used either in addition to the <speaker> element or as an alternative.

Example
<sp>  <speaker>The reverend Doctor Opimian</speaker>  <p>I do not think I have named a single unpresentable fish.</p> </sp> <sp>  <speaker>Mr Gryll</speaker>  <p>Bream, Doctor: there is not much to be said for bream.</p> </sp> <sp>  <speaker>The Reverend Doctor Opimian</speaker>  <p>On the contrary, sir, I think there is much to be said for him. In the first place [...]</p>  <p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I    will forbear [...]</p> </sp>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="speaker"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <sequence minOccurs="1"
   maxOccurs="unbounded">
   <alternate>
    <elementRef key="lg"/>
    <classRef key="model.lLike"/>
    <classRef key="model.pLike"/>
    <classRef key="model.listLike"/>
    <classRef key="model.stageLike"/>
    <classRef key="model.attributable"/>
   </alternate>
   <alternate>
    <classRef key="model.global"
     minOccurs="0" maxOccurs="unbounded"/>
    <elementRef key="q"/>
   </alternate>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element sp
{
   tei_att.global.attributes,
   tei_att.ascribed.directed.attributes,
   (
      tei_model.global*,
      ( ( tei_speaker, tei_model.global* )? ),
      (
         (
            (
               tei_lg
             | tei_model.lLike
             | tei_model.pLike
             | tei_model.listLike
             | tei_model.stageLike
             | tei_model.attributable
            ),
            ( tei_model.global* | tei_q )
         )+
      )
   )
}

1.269. <speaker>

<speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.13.2. Core Tags for Drama]
Modulecore
Attributes
Contained by
core: sp
May contain
Note

This element may be used to transcribe which character is speaking in a dramatic text as indicated by the source text; the who attribute of an <sp> element may be used to point to another element (typically a <role>) which provides information about the character speaking. Either or both may be used.

Example
<sp who="#ni #rsa">  <speaker>Nancy and Robert</speaker>  <stage type="delivery">(speaking simultaneously)</stage>  <p>The future? ...</p> </sp> <list type="speakers">  <item xml:id="ni"/>  <item xml:id="rsa"/> </list>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element speaker { tei_att.global.attributes, tei_macro.phraseSeq }

1.270. <specDesc>

<specDesc> (specification description) indicates that a description of the specified element, class, or macro should be included at this point within a document. [23.1.2. Element and Attribute Descriptions]
Moduletagdocs
Attributes
key(identifier) supplies the identifier of the documentary element or class for which a description is to be obtained.
StatusRequired
Datatypeteidata.name
<specDesc key="emph"/>
Note

The value should match the ident of a documentary element (that is, a member of att.identified).

atts(attributes) supplies attribute names for which descriptions should additionally be obtained.
StatusRecommended
Datatype0–∞ occurrences of teidata.name separated by whitespace
<specDesc key="foreign"  atts="usage xml:lang"/>
Note

The attribute names listed may include both attributes inherited from a class and those defined explicitly for the associated element.

Member of
Contained by
May containEmpty element
Note

The description is usually displayed as a label and an item. The list of attributes may include some which are inherited by virtue of an element's class membership; descriptions for such attributes may also be retrieved using another <specDesc>, this time pointing at the relevant class.

Example
<specDesc key="orth"/>
Example
<specDesc key="emph"/>
Example
<specDesc key="foreign"  atts="usage xml:lang"/>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element specDesc
{
   tei_att.global.attributes,
   attribute key { text },
   attribute atts { list { * } }?,
   empty
}

1.271. <specGrp>

<specGrp> (specification group) contains any convenient grouping of specifications for use within the current module. [23.2. Modules and Schemas]
Moduletagdocs
Attributes
Member of
Contained by
May contain
Note

A specification group is referenced by means of its xml:id attribute. The declarations it contains may be included in a <schemaSpec> or <moduleSpec> element only by reference (using a <specGrpRef> element): it may not be nested within a <moduleSpec> element.

Different ODD processors may generate representations of the specifications contained by a <specGrp> in different concrete syntaxes.

Example
<specGrp xml:id="xDAILC">  <elementSpec ident="s"> <!-- ... -->  </elementSpec>  <elementSpec ident="cl"> <!-- ... -->  </elementSpec>  <elementSpec ident="w"> <!-- ... -->  </elementSpec>  <elementSpec ident="m"> <!-- ... -->  </elementSpec>  <elementSpec ident="c"> <!-- ... -->  </elementSpec> </specGrp>
This specification group with identifier xDAILC contains specifications for the elements <s>,<cl>,<w>, etc.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <classRef key="model.oddDecl"/>
  <classRef key="model.oddRef"/>
  <classRef key="model.divPart"/>
  <elementRef key="listRef"/>
 </alternate>
</content>
    
Schema Declaration
element specGrp
{
   tei_att.global.attributes,
   ( tei_model.oddDecl | tei_model.oddRef | tei_model.divPart | tei_listRef )*
}

1.272. <specGrpRef>

<specGrpRef> (reference to a specification group) indicates that the declarations contained by the <specGrp> referenced should be inserted at this point. [23.2. Modules and Schemas]
Moduletagdocs
Attributes
targetpoints at the specification group which logically belongs here.
StatusRequired
Datatypeteidata.pointer
Member of
Contained by
May containEmpty element
Note

In ODD documentation processing, a <specGrpRef> usually produces a comment indicating that a set of declarations printed in another section will be inserted at this point in the <specGrp> being discussed. In schema processing, the contents of the specified <specGrp> are made available for inclusion in the generated schema.

The specification group identified by the target attribute will normally be part of the current ODD document.

Example
<p>This part of the module contains declarations for names of persons, places, and organisations: <specGrpRef target="#names.pers"/>  <specGrpRef target="#names.place"/>  <specGrpRef target="#names.org"/> </p> <!-- elsewhere --> <specGrp xml:id="names.pers"> <!--... --> </specGrp> <!-- elsewhere --> <specGrp xml:id="names.place"> <!--... --> </specGrp> <!-- elsewhere --> <specGrp xml:id="names.org"> <!--... --> </specGrp>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element specGrpRef
{
   tei_att.global.attributes,
   attribute target { text },
   empty
}

1.273. <specList>

<specList> (specification list) marks where a list of descriptions is to be inserted into the prose documentation. [23.1.2. Element and Attribute Descriptions]
Moduletagdocs
Attributes
Member of
Contained by
May contain
tagdocs: specDesc
Example
<specList>  <specDesc key="refState"   atts="delim length"/>  <specDesc key="div"/> </specList>
Content model
<content>
 <elementRef key="specDesc" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element specList { tei_att.global.attributes, tei_specDesc+ }

1.274. <sponsor>

<sponsor> (sponsor) specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Sponsors give their intellectual authority to a project; they are to be distinguished from funders (see element <funder>), who provide the funding but do not necessarily take intellectual responsibility.

Example
<sponsor>Association for Computers and the Humanities</sponsor> <sponsor>Association for Computational Linguistics</sponsor> <sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element sponsor
{
   tei_att.global.attributes,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   attribute calendar { list { + } }?,
   tei_macro.phraseSeq.limited
}

1.275. <stage>

<stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.13.2. Core Tags for Drama 3.13. Passages of Verse or Drama 7.2.4. Stage Directions]
Modulecore
Attributes
typeindicates the kind of stage direction.
StatusRecommended
Datatype0–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
setting
describes a setting.
entrance
describes an entrance.
exit
describes an exit.
business
describes stage business.
novelistic
is a narrative, motivating stage direction.
delivery
describes how a character speaks.
modifier
gives some detail about a character.
location
describes a location.
mixed
more than one of the above
Note

If the value mixed is used, it must be the only value. Multiple values may however be supplied if a single stage direction performs multiple functions, for example is both an entrance and a modifier.

Member of
Contained by
May contain
Note

The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction.

Example
<stage type="setting">A curtain being drawn.</stage> <stage type="setting">Music</stage> <stage type="entrance">Enter Husband as being thrown off his horse and falls.</stage> <!-- Middleton : Yorkshire Tragedy --> <stage type="exit">Exit pursued by a bear.</stage> <stage type="business">He quickly takes the stone out.</stage> <stage type="delivery">To Lussurioso.</stage> <stage type="novelistic">Having had enough, and embarrassed for the family.</stage> <!-- Lorraine Hansbury : a raisin in in the sun --> <stage type="modifier">Disguised as Ansaldo.</stage> <stage type="entrance modifier">Enter Latrocinio disguised as an empiric</stage> <!-- Middleton: The Widow --> <stage type="location">At a window.</stage> <stage rend="inlinetype="delivery">Aside.</stage>
Example
<l>Behold. <stage n="*place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when    straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on    two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the  <hi>Prologue</hi> was spoken, which being ended, they descended in    order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our Poet knowing our free hearts</l>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element stage
{
   tei_att.ascribed.directed.attributes,
   tei_att.global.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   attribute type
   {
      list
      {
         (
            "setting"
          | "entrance"
          | "exit"
          | "business"
          | "novelistic"
          | "delivery"
          | "modifier"
          | "location"
          | "mixed"
         )*
      }
   }?,
   tei_macro.specialPara
}

1.276. <state>

<state> (state) contains a description of some status or quality attributed to a person, place, or organization often at some specific time or for a specific date range. [14.3.1. Basic Principles 14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<state ref="#SCHOLtype="status">  <label>scholar</label> </state>
Example
<org>  <orgName notAfter="1960">The Silver Beetles</orgName>  <orgName notBefore="1960">The Beatles</orgName>  <state type="membershipfrom="1960-08"   to="1962-05">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Stuart Sutcliffe</persName>    <persName>Pete Best</persName>   </desc>  </state>  <state type="membershipnotBefore="1963">   <desc>    <persName>John Lennon</persName>    <persName>Paul McCartney</persName>    <persName>George Harrison</persName>    <persName>Ringo Starr</persName>   </desc>  </state> </org>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="state" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence>
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element state
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.typed.attributes,
   tei_att.naming.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      (
         tei_state+
       | (
            tei_model.headLike*,
            tei_model.pLike+,
            ( tei_model.noteLike | tei_model.biblLike )*
         )
       | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
      )
   )
}

1.277. <stdVals>

<stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 16.3.2. Declarable Elements]
Moduleheader
Attributes
Member of
Contained by
May contain
core: p
Example
<stdVals>  <p>All integer numbers are left-filled with zeroes to 8 digits.</p> </stdVals>
Content model
<content>
 <classRef key="model.pLike" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element stdVals
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_model.pLike+
}

1.278. <street>

<street> contains a full street address including any name or number identifying a building as well as the name of the street or route on which it is located. [3.6.2. Addresses]
Modulecore
Attributes
Member of
Contained by
core: address
May contain
Note

The order and presentation of house names and numbers and street names, etc., may vary considerably in different countries. The encoding should reflect the order which is appropriate in the country concerned.

Example
<street>via della Faggiola, 36</street>
Example
<street>  <name>Duntaggin</name>, 110 Southmoor Road </street>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element street { tei_att.global.attributes, tei_macro.phraseSeq }

1.279. <styleDefDecl>

<styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration]
Moduleheader
Attributes
Member of
Contained by
header: encodingDesc
May contain
core: p
Example
<styleDefDecl scheme="css"  schemeVersion="2.1"/> <!-- ... --> <tagsDecl>  <rendition xml:id="boldface">font-weight: bold;</rendition>  <rendition xml:id="italicstyle">font-style: italic;</rendition> </tagsDecl>
Content model
<content>
 <classRef key="model.pLike" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element styleDefDecl
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.styleDef.attributes,
   tei_model.pLike*
}

1.280. <surname>

<surname> (surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name. [14.2.1. Personal Names]
Modulenamesdates
Attributes
Member of
Contained by
May contain
Example
<surname type="combine">St John Stevas</surname>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element surname
{
   tei_att.global.attributes,
   tei_att.personal.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.281. <tag>

<tag> (tag) contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [23. Documentation Elements]
Moduletagdocs
Attributes
typeindicates the type of XML tag intended
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Legal values are:
start
a start-tag, with delimiters < and > is intended
end
an end-tag, with delimiters </ and > is intended
empty
an empty tag, with delimiters < and /> is intended
pi
a pi (processing instruction), with delimiters <? and ?> is intended
comment
a comment, with delimiters <!-- and --> is intended
ms
a marked-section, with delimiters <[CDATA[ and ]]> is intended
schemesupplies the name of the schema in which this tag is defined.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
TEI
(text encoding initiative) This tag is defined as part of the TEI scheme.[Default]
DBK
(docbook) this tag is part of the Docbook scheme.
XX
(unknown) this tag is part of an unknown scheme.
Schematron
HTML
Member of
Contained by
May containCharacter data only
Example
Mark the start of each italicised phrase with a <tag>hi rend="it"</tag> tag, and its end with a <tag type="end">hi</tag> tag. <tag type="comment">Example updated on 2008-04-05</tag>
Content model
<content>
 <textNode/>
</content>
    
Schema Declaration
element tag
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { "start" | "end" | "empty" | "pi" | "comment" | "ms" }?,
   attribute scheme { text }?,
   text
}

1.282. <tagUsage>

<tagUsage> (element usage) documents the usage of a specific element within a specified document. [2.3.4. The Tagging Declaration]
Moduleheader
Attributes
gi(generic identifier) specifies the name (generic identifier) of the element indicated by the tag, within the namespace indicated by the parent <namespace> element.
StatusRequired
Datatypeteidata.name
occursspecifies the number of occurrences of this element within the text.
StatusRecommended
Datatypeteidata.count
withId(with unique identifier) specifies the number of occurrences of this element within the text which bear a distinct value for the global xml:id attribute.
StatusRecommended
Datatypeteidata.count
Contained by
header: namespace
May contain
Example
<tagsDecl partial="true">  <rendition xml:id="itscheme="css"   selector="foreign, hi"> font-style: italic; </rendition> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="28withId="2"> Used to mark English words italicized in the copy text.</tagUsage>   <tagUsage gi="foreign">Used to mark non-English words in the copy text.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Content model
<content>
 <macroRef key="macro.limitedContent"/>
</content>
    
Schema Declaration
element tagUsage
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   attribute gi { text },
   attribute occurs { text }?,
   attribute withId { text }?,
   tei_macro.limitedContent
}

1.283. <tagsDecl>

<tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description]
Moduleheader
Attributes
partialindicates whether the element types listed exhaustively include all those found within <text>, or represent only a subset.
StatusRecommended
Datatypeteidata.truthValue
Note

TEI recommended practice is to specify this attribute. When the <tagUsage> elements inside <tagsDecl> are used to list each of the element types in the associated <text>, the value should be given as false. When the <tagUsage> elements inside <tagsDecl> are used to provide usage information or default renditions for only a subset of the elements types within the associated <text>, the value should be true.

Member of
Contained by
header: encodingDesc
May contain
Example
<tagsDecl partial="true">  <rendition xml:id="rend-itscheme="css"   selector="emph, hi, name, title">font-style: italic;</rendition>  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="hioccurs="467"/>   <tagUsage gi="titleoccurs="45"/>  </namespace>  <namespace name="http://docbook.org/ns/docbook">   <tagUsage gi="paraoccurs="10"/>  </namespace> </tagsDecl>
If the partial attribute were not specified here, the implication would be that the document in question contains only <hi>, <title>, and <para> elements.
Content model
<content>
 <sequence>
  <elementRef key="rendition" minOccurs="0"
   maxOccurs="unbounded"/>
  <elementRef key="namespace" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element tagsDecl
{
   tei_att.global.attributes,
   attribute partial { text }?,
   ( tei_rendition*, tei_namespace* )
}

1.284. <taxonomy>

<taxonomy> (taxonomy) defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration]
Moduleheader
Attributes
Contained by
May contain
Note

Nested taxonomies are common in many fields, so the <taxonomy> element can be nested.

Example
<taxonomy xml:id="tax.b">  <bibl>Brown Corpus</bibl>  <category xml:id="tax.b.a">   <catDesc>Press Reportage</catDesc>   <category xml:id="tax.b.a1">    <catDesc>Daily</catDesc>   </category>   <category xml:id="tax.b.a2">    <catDesc>Sunday</catDesc>   </category>   <category xml:id="tax.b.a3">    <catDesc>National</catDesc>   </category>   <category xml:id="tax.b.a4">    <catDesc>Provincial</catDesc>   </category>   <category xml:id="tax.b.a5">    <catDesc>Political</catDesc>   </category>   <category xml:id="tax.b.a6">    <catDesc>Sports</catDesc>   </category>  </category>  <category xml:id="tax.b.d">   <catDesc>Religion</catDesc>   <category xml:id="tax.b.d1">    <catDesc>Books</catDesc>   </category>   <category xml:id="tax.b.d2">    <catDesc>Periodicals and tracts</catDesc>   </category>  </category> </taxonomy>
Example
<taxonomy>  <category xml:id="literature">   <catDesc>Literature</catDesc>   <category xml:id="poetry">    <catDesc>Poetry</catDesc>    <category xml:id="sonnet">     <catDesc>Sonnet</catDesc>     <category xml:id="shakesSonnet">      <catDesc>Shakespearean Sonnet</catDesc>     </category>     <category xml:id="petraSonnet">      <catDesc>Petrarchan Sonnet</catDesc>     </category>    </category>    <category xml:id="haiku">     <catDesc>Haiku</catDesc>    </category>   </category>   <category xml:id="drama">    <catDesc>Drama</catDesc>   </category>  </category>  <category xml:id="meter">   <catDesc>Metrical Categories</catDesc>   <category xml:id="feet">    <catDesc>Metrical Feet</catDesc>    <category xml:id="iambic">     <catDesc>Iambic</catDesc>    </category>    <category xml:id="trochaic">     <catDesc>trochaic</catDesc>    </category>   </category>   <category xml:id="feetNumber">    <catDesc>Number of feet</catDesc>    <category xml:id="pentameter">     <catDesc>>Pentameter</catDesc>    </category>    <category xml:id="tetrameter">     <catDesc>>Tetrameter</catDesc>    </category>   </category>  </category> </taxonomy> <!-- elsewhere in document --> <lg ana="#shakesSonnet #iambic #pentameter">  <l>Shall I compare thee to a summer's day</l> <!-- ... --> </lg>
Content model
<content>
 <alternate>
  <alternate>
   <alternate minOccurs="1"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
   <sequence>
    <alternate minOccurs="1"
     maxOccurs="unbounded">
     <classRef key="model.descLike"
      minOccurs="1" maxOccurs="1"/>
     <elementRef key="equiv" minOccurs="1"
      maxOccurs="1"/>
     <elementRef key="gloss" minOccurs="1"
      maxOccurs="1"/>
    </alternate>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <elementRef key="category"/>
     <elementRef key="taxonomy"/>
    </alternate>
   </sequence>
  </alternate>
  <sequence>
   <classRef key="model.biblLike"/>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <elementRef key="category"/>
    <elementRef key="taxonomy"/>
   </alternate>
  </sequence>
 </alternate>
</content>
    
Schema Declaration
element taxonomy
{
   tei_att.global.attributes,
   tei_att.datcat.attributes,
   (
      (
         ( tei_category | tei_taxonomy )+
       | (
            ( tei_model.descLike | tei_equiv | tei_gloss )+,
            ( tei_category | tei_taxonomy )*
         )
      )
    | ( tei_model.biblLike, ( tei_category | tei_taxonomy )* )
   )
}

1.285. <teiCorpus>

<teiCorpus> (TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more <TEI> elements, each containing a single text header and a text. [4. Default Text Structure 16.1. Varieties of Composite Text]
Modulecore
Attributes
version(version) specifies the version number of the TEI Guidelines against which this document is valid.
StatusOptional
Datatypeteidata.version
Note

Major editions of the Guidelines have long been informally referred to by a name made up of the letter P (for Proposal) followed by a digit. The current release is one of the many releases of the fifth major edition of the Guidelines, known as P5. This attribute may be used to associate a TEI document with a specific release of the P5 Guidelines, in the absence of a more precise association provided by the source attribute on the associated <schemaSpec>.

Member of
Contained by
core: teiCorpus
May contain
core: teiCorpus
header: teiHeader
textstructure: TEI text
Note

Should contain one TEI header for the corpus, and a series of <TEI> elements, one for each text.

Example
<teiCorpus version="3.3.0" xmlns="http://www.tei-c.org/ns/1.0">  <teiHeader> <!-- header for corpus -->  </teiHeader>  <TEI>   <teiHeader> <!-- header for first text -->   </teiHeader>   <text> <!-- content of first text -->   </text>  </TEI>  <TEI>   <teiHeader> <!-- header for second text -->   </teiHeader>   <text> <!-- content of second text -->   </text>  </TEI> <!-- more TEI elements here --> </teiCorpus>
Content model
<content>
 <sequence>
  <elementRef key="teiHeader"/>
  <classRef key="model.resource"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.describedResource"
   minOccurs="1" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element teiCorpus
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   attribute version { text }?,
   ( tei_teiHeader, tei_model.resource*, tei_model.describedResource+ )
}

1.286. <teiHeader>

<teiHeader> (TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources. [2.1.1. The TEI Header and Its Components 16.1. Varieties of Composite Text]
Moduleheader
Attributes
Contained by
core: teiCorpus
textstructure: TEI
May contain
Note

One of the few elements unconditionally required in any TEI document.

Example
<teiHeader>  <fileDesc>   <titleStmt>    <title>Shakespeare: the first folio (1623) in electronic form</title>    <author>Shakespeare, William (1564–1616)</author>    <respStmt>     <resp>Originally prepared by</resp>     <name>Trevor Howard-Hill</name>    </respStmt>    <respStmt>     <resp>Revised and edited by</resp>     <name>Christine Avern-Carr</name>    </respStmt>   </titleStmt>   <publicationStmt>    <distributor>Oxford Text Archive</distributor>    <address>     <addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>    </address>    <idno type="OTA">119</idno>    <availability>     <p>Freely available on a non-commercial basis.</p>    </availability>    <date when="1968">1968</date>   </publicationStmt>   <sourceDesc>    <bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,        1968)</bibl>   </sourceDesc>  </fileDesc>  <encodingDesc>   <projectDesc>    <p>Originally prepared for use in the production of a series of old-spelling        concordances in 1968, this text was extensively checked and revised for use during the        editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>   </projectDesc>   <editorialDecl>    <correction>     <p>Turned letters are silently corrected.</p>    </correction>    <normalization>     <p>Original spelling and typography is retained, except that long s and ligatured          forms are not encoded.</p>    </normalization>   </editorialDecl>   <refsDecl xml:id="ASLREF">    <cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"     replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">     <p>A reference is created by assembling the following, in the reverse order as that          listed here: <list>       <item>the <att>n</att> value of the preceding <gi>lb</gi>       </item>       <item>a period</item>       <item>the <att>n</att> value of the ancestor <gi>div2</gi>       </item>       <item>a space</item>       <item>the <att>n</att> value of the parent <gi>div1</gi>       </item>      </list>     </p>    </cRefPattern>   </refsDecl>  </encodingDesc>  <revisionDesc>   <list>    <item>     <date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>    <item>     <date when="1989-03-01">1 Mar 89</date> LB made new file</item>   </list>  </revisionDesc> </teiHeader>
Content model
<content>
 <sequence>
  <elementRef key="fileDesc"/>
  <classRef key="model.teiHeaderPart"
   minOccurs="0" maxOccurs="unbounded"/>
  <elementRef key="revisionDesc"
   minOccurs="0"/>
 </sequence>
</content>
    
Schema Declaration
element teiHeader
{
   tei_att.global.attributes,
   ( tei_fileDesc, tei_model.teiHeaderPart*, tei_revisionDesc? )
}

1.287. <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Modulecore
Attributes
Member of
Contained by
May contain
Note

When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute.

In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion.

As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.

Example
A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.
Example
We may define <term xml:id="TDPV1rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We may define <term ref="#TDPV2rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>
Example
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2rend="sc">discoursal point of view</term> below.
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element term
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.pointing.attributes,
   tei_att.typed.attributes,
   tei_att.canonical.attributes,
   tei_att.sortable.attributes,
   tei_att.cReferencing.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.288. <terrain>

<terrain> (terrain) contains information about the physical terrain of a place. [14.3.4.3. States, Traits, and Events]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Example
<place xml:id="KERG">  <placeName>Kerguelen Islands</placeName> <!-- ... -->  <terrain>   <desc>antarctic tundra</desc>  </terrain> <!-- ... --> </place>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <classRef key="model.headLike"
   minOccurs="0" maxOccurs="unbounded"/>
  <alternate>
   <classRef key="model.pLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <classRef key="model.labelLike"
    minOccurs="1" maxOccurs="unbounded"/>
  </alternate>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.noteLike"/>
   <classRef key="model.biblLike"/>
  </alternate>
  <elementRef key="terrain" minOccurs="0"
   maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element terrain
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      tei_model.headLike*,
      ( tei_model.pLike+ | tei_model.labelLike+ ),
      ( tei_model.noteLike | tei_model.biblLike )*,
      tei_terrain*
   )
}

1.289. <text>

<text> (text) contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 16.1. Varieties of Composite Text]
Moduletextstructure
Attributes
Member of
Contained by
core: teiCorpus
textstructure: TEI group
May contain
Note

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

Example
<text>  <front>   <docTitle>    <titlePart>Autumn Haze</titlePart>   </docTitle>  </front>  <body>   <l>Is it a dragonfly or a maple leaf</l>   <l>That settles softly down upon the water?</l>  </body> </text>
ExampleThe body of a text may be replaced by a group of nested texts, as in the following schematic:
<text>  <front> <!-- front matter for the whole group -->  </front>  <group>   <text> <!-- first text -->   </text>   <text> <!-- second text -->   </text>  </group> </text>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="front"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
  <alternate>
   <elementRef key="body"/>
   <elementRef key="group"/>
  </alternate>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <elementRef key="back"/>
   <classRef key="model.global"
    minOccurs="0" maxOccurs="unbounded"/>
  </sequence>
 </sequence>
</content>
    
Schema Declaration
element text
{
   tei_att.global.attributes,
   tei_att.declaring.attributes,
   tei_att.typed.attributes,
   tei_att.written.attributes,
   (
      tei_model.global*,
      ( ( tei_front, tei_model.global* )? ),
      ( tei_body | tei_group ),
      tei_model.global*,
      ( ( tei_back, tei_model.global* )? )
   )
}

1.290. <textClass>

<textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification]
Moduleheader
Attributes
Member of
Contained by
header: profileDesc
May contain
Example
<taxonomy>  <category xml:id="acprose">   <catDesc>Academic prose</catDesc>  </category> <!-- other categories here --> </taxonomy> <!-- ... --> <textClass>  <catRef target="#acprose"/>  <classCode scheme="http://www.udcc.org">001.9</classCode>  <keywords scheme="http://authorities.loc.gov">   <list>    <item>End of the world</item>    <item>History - philosophy</item>   </list>  </keywords> </textClass>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <elementRef key="classCode"/>
  <elementRef key="catRef"/>
  <elementRef key="keywords"/>
 </alternate>
</content>
    
Schema Declaration
element textClass
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   ( tei_classCode | tei_catRef | tei_keywords )*
}

1.291. <textLang>

<textLang> (text language) describes the languages and writing systems identified within the bibliographic work being described, rather than its description. [3.12.2.4. Imprint, Size of a Document, and Reprint Information 11.6.6. Languages and Writing Systems]
Modulecore
Attributes
mainLang(main language) supplies a code which identifies the chief language used in the bibliographic work.
StatusOptional
Datatypeteidata.language
otherLangs(other languages) one or more codes identifying any other languages used in the bibliographic work.
StatusOptional
Datatype0–∞ occurrences of teidata.language separated by whitespace
Member of
Contained by
May contain
Note

This element should not be used to document the languages or writing systems used for the bibliographic or manuscript description itself: as for all other TEI elements, such information should be provided by means of the global xml:lang attribute attached to the element containing the description.

In all cases, languages should be identified by means of a standardized ‘language tag’ generated according to BCP 47. Additional documentation for the language may be provided by a <language> element in the TEI header.

Example
<textLang mainLang="enotherLangs="la"> Predominantly in English with Latin glosses</textLang>
Content model
<content>
 <macroRef key="macro.specialPara"/>
</content>
    
Schema Declaration
element textLang
{
   tei_att.global.attributes,
   attribute mainLang { text }?,
   attribute otherLangs { list { * } }?,
   tei_macro.specialPara
}

1.292. <textNode>

<textNode> indicates the presence of a text node in a content model [23. Documentation Elements]
Moduletagdocs
Attributes
Member of
Contained by
May containEmpty element
Example
<content>  <alternate minOccurs="0"   maxOccurs="unbounded">   <textNode/>   <elementRef key="hi"/>   <elementRef key="seg"/>  </alternate> </content>
Content model
<content>
 <empty/>
</content>
    
Schema Declaration
element textNode { tei_att.global.attributes, empty }

1.293. <time>

<time> (time) contains a phrase defining a time of day in any format. [3.6.4. Dates and Times]
Modulecore
Attributes
Member of
Contained by
May contain
Example
As he sat smiling, the quarter struck — <time when="11:45:00">the quarter to twelve</time>.
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element time
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.calendarSystem.attributes,
   tei_att.canonical.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.typed.attributes,
   tei_att.cmc.attributes,
   ( text | tei_model.gLike | tei_model.phrase | tei_model.global )*
}

1.294. <title>

<title> (title) contains a title for any kind of work. [3.12.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement]
Modulecore
Attributes
typeclassifies the title according to some convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Sample values include:
main
main title
sub
(subordinate) subtitle, title of part
alt
(alternate) alternate title, often in another language, by which the work is also known
short
abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work functioning as a title
Note

This attribute is provided for convenience in analysing titles and processing them according to their type; where such specialized processing is not necessary, there is no need for such analysis, and the entire title, including subtitles and any parallel titles, may be enclosed within a single <title> element.

calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
levelindicates the bibliographic level for a title, that is, whether it identifies an article, book, journal, series, or unpublished material.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
a
(analytic) the title applies to an analytic item, such as an article, poem, or other work published as part of a larger item.
m
(monographic) the title applies to a monograph such as a book or other item considered to be a distinct publication, including single volumes of multi-volume works
j
(journal) the title applies to any serial or periodical publication such as a journal, magazine, or newspaper
s
(series) the title applies to a series of otherwise distinct publications such as a collection
u
(unpublished) the title applies to any unpublished material (including theses and dissertations unless published by a commercial press)
Note

The level of a title is sometimes implied by its context: for example, a title appearing directly within an <analytic> element is ipso facto of level ‘a’, and one appearing within a <series> element of level ‘s’. For this reason, the level attribute is not required in contexts where its value can be unambiguously inferred. Where it is supplied in such contexts, its value should not contradict the value implied by its parent element.

Member of
Contained by
May contain
Note

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

Example
<title>Information Technology and the Research Process: Proceedings of a conference held at Cranfield Institute of Technology, UK, 18–21 July 1989</title>
Example
<title>Hardy's Tess of the D'Urbervilles: a machine readable edition</title>
Example
<title type="full">  <title type="main">Synthèse</title>  <title type="sub">an international journal for    epistemology, methodology and history of    science</title> </title>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element title
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.cmc.attributes,
   attribute type { text }?,
   attribute calendar { list { + } }?,
   attribute level { "a" | "m" | "j" | "s" | "u" }?,
   tei_macro.paraContent
}

1.295. <titlePage>

<titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages]
Moduletextstructure
Attributes
typeclassifies the title page according to any convenient typology.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Note

This attribute allows the same element to be used for volume title pages, series title pages, etc., as well as for the ‘main’ title page of a work.

Member of
Contained by
textstructure: back front
May contain
Example
<titlePage>  <docTitle>   <titlePart type="main">THOMAS OF Reading.</titlePart>   <titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>  </docTitle>  <docEdition>Now the fourth time corrected and enlarged</docEdition>  <byline>By T.D.</byline>  <figure>   <head>TP</head>   <p>Thou shalt labor till thou returne to duste</p>   <figDesc>Printers Ornament used by TP</figDesc>  </figure>  <docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>   <date>1612.</date>  </docImprint> </titlePage>
Content model
<content>
 <sequence>
  <classRef key="model.global"
   minOccurs="0" maxOccurs="unbounded"/>
  <classRef key="model.titlepagePart"/>
  <alternate minOccurs="0"
   maxOccurs="unbounded">
   <classRef key="model.titlepagePart"/>
   <classRef key="model.global"/>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element titlePage
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { text }?,
   (
      tei_model.global*,
      tei_model.titlepagePart,
      ( tei_model.titlepagePart | tei_model.global )*
   )
}

1.296. <titlePart>

<titlePart> (title part) contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages]
Moduletextstructure
Attributes
type(type) specifies the role of this subdivision of the title.
Derived fromatt.typed
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
main
(main) main title of the work[Default]
sub
(subordinate) subtitle of the work
alt
(alternate) alternative title of the work
short
(short) abbreviated form of title
desc
(descriptive) descriptive paraphrase of the work
Member of
Contained by
textstructure: back docTitle front titlePage
May contain
Example
<docTitle>  <titlePart type="main">THE FORTUNES    AND MISFORTUNES Of the FAMOUS    Moll Flanders, &amp;c.  </titlePart>  <titlePart type="desc">Who was BORN in NEWGATE,    And during a Life of continu'd Variety for    Threescore Years, besides her Childhood, was    Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof    once to her own Brother) Twelve Year a <hi>Thief,</hi>    Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>,    at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a  <hi>Penitent</hi>.</titlePart> </docTitle>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element titlePart
{
   tei_att.global.attributes,
   tei_att.typed.attribute.subtype,
   attribute type { "main" | "sub" | "alt" | "short" | "desc" }?,
   tei_macro.paraContent
}

1.297. <titleStmt>

<titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description]
Moduleheader
Attributes
Contained by
May contain
Example
<titleStmt>  <title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>  <respStmt>   <resp>compiled by</resp>   <name>P.J. Lucas</name>  </respStmt> </titleStmt>
Content model
<content>
 <sequence>
  <elementRef key="title" minOccurs="1"
   maxOccurs="unbounded"/>
  <classRef key="model.respLike"
   minOccurs="0" maxOccurs="unbounded"/>
 </sequence>
</content>
    
Schema Declaration
element titleStmt
{
   tei_att.global.attributes,
   ( tei_title+, tei_model.respLike* )
}

1.298. <trailer>

<trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions]
Moduletextstructure
Attributes
Member of
Contained by
May contain
Example
<trailer>Explicit pars tertia</trailer>
Example
<trailer>  <l>In stead of FINIS this advice <hi>I</hi> send,</l>  <l>Let Rogues and Thieves beware of <lb/>   <hi>Hamans</hi> END.</l> </trailer>
From EEBO A87070
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <elementRef key="lg"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.lLike"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Schema Declaration
element trailer
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.placement.attributes,
   tei_att.written.attributes,
   tei_att.cmc.attributes,
   (
      text
    | tei_lg
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.lLike
    | tei_model.global
   )*
}

1.299. <trait>

<trait> (trait) contains a description of some status or quality attributed to a person, place, or organization typically, but not necessarily, independent of the volition or action of the holder and usually not at some specific time or for a specific date range. [14.3.1. Basic Principles 14.3.2.1. Personal Characteristics]
Modulenamesdates
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
May contain
Note

Where there is confusion between <trait> and <state> the more general purpose element <state> should be used even for unchanging characteristics. If you wish to distinguish between characteristics that are generally perceived to be time-bound states and those assumed to be fixed traits, then <trait> is available for the more static of these. The <state> element encodes characteristics which are sometimes assumed to change, often at specific times or over a date range, whereas the <trait> elements are used to record characteristics, such as eye-colour, which are less subject to change. Traits are typically, but not necessarily, independent of the volition or action of the holder.

Example
<trait type="physical">  <label>Eye colour</label>  <desc>Blue</desc> </trait>
Content model
<content>
 <sequence>
  <elementRef key="precision" minOccurs="0"
   maxOccurs="unbounded"/>
  <alternate>
   <elementRef key="trait" minOccurs="1"
    maxOccurs="unbounded"/>
   <sequence>
    <classRef key="model.headLike"
     minOccurs="0" maxOccurs="unbounded"/>
    <classRef key="model.pLike"
     minOccurs="1" maxOccurs="unbounded"/>
    <alternate minOccurs="0"
     maxOccurs="unbounded">
     <classRef key="model.noteLike"/>
     <classRef key="model.biblLike"/>
    </alternate>
   </sequence>
   <alternate minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.labelLike"/>
    <classRef key="model.noteLike"/>
    <classRef key="model.biblLike"/>
   </alternate>
  </alternate>
 </sequence>
</content>
    
Schema Declaration
element trait
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.editLike.attributes,
   tei_att.naming.attributes,
   tei_att.typed.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute calendar { list { + } }?,
   (
      precision*,
      (
         tei_trait+
       | (
            tei_model.headLike*,
            tei_model.pLike+,
            ( tei_model.noteLike | tei_model.biblLike )*
         )
       | ( tei_model.labelLike | tei_model.noteLike | tei_model.biblLike )*
      )
   )
}

1.300. <unclear>

<unclear> (unclear) contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [12.3.3.1. Damage, Illegibility, and Supplied Text 3.5.3. Additions, Deletions, and Omissions]
Modulecore
Attributes
reasonindicates why the material is hard to transcribe.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
illegible
(illegible)
inaudible
(inaudible)
faded
(faded)
background_noise
(background noise)
eccentric_ductus
(eccentric ductus) indicates illegibility due to an unusual, awkward, or incompetent execution of a glyph or glyphs
<div>  <head>Rx</head>  <p>500 mg <unclear reason="illegible">placebo</unclear>  </p> </div>
Note

One or more words may be used to describe the reason; usually each word will refer to a single cause.

agentWhere the difficulty in transcription arises from damage, categorizes the cause of the damage, if it can be identified.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
rubbing
damage results from rubbing of the leaf edges
mildew
damage results from mildew on the leaf surface
smoke
damage results from smoke
Member of
Contained by
May contain
Note

The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 22. Certainty, Precision, and Responsibility.

The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 12.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.

The hand attribute points to a definition of the hand concerned, as further discussed in section 12.3.2.1. Document Hands.

Example
<u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u>
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
    
Schema Declaration
element unclear
{
   tei_att.global.attributes,
   tei_att.editLike.attributes,
   tei_att.dimensions.attributes,
   tei_att.cmc.attributes,
   attribute reason
   {
      list
      {
         (
            "illegible"
          | "inaudible"
          | "faded"
          | "background_noise"
          | "eccentric_ductus"
         )+
      }
   }?,
   attribute agent { text }?,
   tei_macro.paraContent
}

1.301. <unit>

<unit> contains a symbol, a word or a phrase referring to a unit of measurement in any kind of formal or informal system. [3.6.3. Numbers and Measures]
Modulecore
Attributes
Member of
Contained by
May contain
ExampleHere is an example of a <unit> element holding a unitRef attribute that points to a definition of the unit in the TEI header.
<measure>  <num>3</num>  <unit unitRef="#ell">ells</unit> </measure> <!-- In the TEI Header: --> <encodingDesc>  <unitDecl>   <unitDef xml:id="ell">    <label>ell</label>    <placeName ref="#iceland"/>    <desc>A unit of measure for cloth, roughly equivalent to 18 inches, or from an adult male’s elbow to the tip of the middle finger.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<measure>  <num>2</num>  <unit>kg</unit> </measure>
Example
<measure type="value">  <num>3</num>  <unit type="timeunit="min">minute</unit> </measure>
Example
<measure type="interval">  <num atLeast="1.2">1.2</num> to <num atMost="5.6">5.6</num>  <unit type="velocityunit="km/h">km/h</unit> </measure>
Example
<p>Light travels at <num value="3E10">3×10^10</num>  <unit type="rateunit="cm/s">   <unit type="space">cm</unit> per <unit type="time">second</unit>  </unit>.</p>
Content model
<content>
 <macroRef key="macro.phraseSeq"/>
</content>
    
Schema Declaration
element unit
{
   tei_att.global.attributes,
   tei_att.typed.attributes,
   tei_att.measurement.attributes,
   tei_att.cmc.attributes,
   tei_macro.phraseSeq
}

1.302. <unitDecl>

<unitDecl> (unit declarations) provides information about units of measurement that are not members of the International System of Units. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Member of
Contained by
header: encodingDesc
May contain
header: unitDef
Example
<unitDecl>  <unitDef xml:id="type="weight">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">kin</label>   <conversion fromUnit="#両toUnit="#斤"    formula="16"/>  </unitDef>  <unitDef xml:id="type="weight">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">ryo</label>   <conversion fromUnit="#分toUnit="#両"    formula="4"/>  </unitDef>  <unitDef xml:id="type="weight">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">Bu</label>   <conversion fromUnit="#銖toUnit="#分"    formula="6"/>  </unitDef>  <unitDef xml:id="type="weight">   <label xml:lang="ja"></label>   <label xml:lang="ja-Latn">Shu</label>  </unitDef> </unitDecl>
Content model
<content>
 <elementRef key="unitDef" minOccurs="1"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element unitDecl
{
   tei_att.canonical.attributes,
   tei_att.datable.attributes,
   tei_att.global.attributes,
   attribute calendar { list { + } }?,
   tei_unitDef+
}

1.303. <unitDef>

<unitDef> (unit definition) contains descriptive information related to a specific unit of measurement. [2.3.9. The Unit Declaration]
Moduleheader
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
Deprecatedwill be removed on 2024-11-11
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
Contained by
header: unitDecl
May contain
Example
<unitDecl>  <unitDef xml:id="pechystype="length">   <label>πῆχυς</label>   <placeName ref="#athens"/>   <conversion fromUnit="#daktylos"    toUnit="#pechysformula="$fromUnit div 24"/>   <desc>Equivalent to a cubit or 24 daktyloi.</desc>  </unitDef>  <unitDef xml:id="daktylostype="length">   <label>δάκτυλος</label>   <placeName ref="#athens"/>   <desc>A basic unit of length equivalent to one finger (or the size of a thumb) in ancient Greece.</desc>  </unitDef> </unitDecl>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.labelLike"
   minOccurs="1"/>
  <classRef key="model.placeNamePart"
   minOccurs="0"/>
  <elementRef key="conversion"
   minOccurs="0"/>
  <elementRef key="unit" minOccurs="0"/>
 </alternate>
</content>
    
Schema Declaration
element unitDef
{
   tei_att.global.attributes,
   tei_att.datable.attributes,
   tei_att.canonical.attributes,
   tei_att.typed.attributes,
   attribute calendar { list { + } }?,
   (
      tei_model.labelLike
    | tei_model.placeNamePart?
    | tei_conversion?
    | tei_unit?
   )+
}

1.305. <valDesc>

<valDesc> (value description) specifies any semantic or syntactic constraint on the value that an attribute may take, additional to the information carried by the <datatype> element. [23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
Contained by
tagdocs: attDef
May contain
Example
<valDesc>must point to another <gi>align</gi> element logically preceding this one.</valDesc>
Content model
<content>
 <macroRef key="macro.phraseSeq.limited"/>
</content>
    
Schema Declaration
element valDesc
{
   tei_att.global.attributes,
   tei_att.translatable.attributes,
   tei_att.combinable.attributes,
   tei_macro.phraseSeq.limited
}

1.306. <valItem>

<valItem> documents a single value in a predefined list of values. [23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
identspecifies the value concerned.
StatusRequired
Datatypeteidata.text
Contained by
tagdocs: valList
May contain
Example
<valItem ident="dub">  <altIdent xml:lang="fr">dou</altIdent>  <equiv name="unknown"/>  <gloss>dubious</gloss>  <desc>used when the application of this element is doubtful or uncertain</desc> </valItem>
ExampleThe <remarks> element is only allowed within <valItem> if the <desc> element is also present:
<valList type="closed">  <valItem ident="border">   <desc>used to signify that there is border around a page.</desc>  </valItem>  <valItem ident="border-rule">   <desc>used to signify that there is a border made of ruled lines.</desc>  </valItem>  <valItem ident="border-ornamental">   <desc>used to signify that there is an ornamental border.</desc>  </valItem>  <valItem ident="catch">   <gloss>catchword</gloss>   <desc>for catch words.</desc>  </valItem>  <valItem ident="lineNum">   <gloss>line number</gloss>   <desc>for printed line numbers (usually in poetry).</desc>  </valItem>  <valItem ident="listHead">   <gloss>list heading</gloss>   <desc>for headings of lists or similar constructs; often used in tables of contents for the   <q>page</q> heading.</desc>  </valItem>  <valItem ident="pageNum">   <gloss>page number</gloss>   <desc>for page numbers.</desc>  </valItem>  <valItem ident="pressFig">   <gloss>press figure</gloss>   <desc>for press figures. These are usually numbers, but are not sequential or regularly      printed like signatures.</desc>  </valItem>  <valItem ident="sig">   <gloss>signature</gloss>   <desc>for printed signatures.</desc>  </valItem>  <valItem ident="unknown">   <desc>for a metawork whose function you do not know.</desc>  </valItem>  <valItem ident="vol">   <gloss>volume number</gloss>   <desc>for printed volume numbers.</desc>  </valItem>  <valItem ident="other">   <desc>anything not covered by the above values.</desc>   <remarks>    <p>Used for an ornament, decorated tool line, or symbol(s) that is not officially a        delimiter (and thus there is no element on which to put <val>pre()</val> or    <val>post()</val>) but is used to fill space at the bottom of a page so that a    <gi>floatingText</gi> or similar can start at the top of the next.</p>   </remarks>  </valItem> </valList>
Content model
<content>
 <sequence>
  <classRef key="model.identSynonyms"
   minOccurs="0" maxOccurs="unbounded"/>
  <sequence minOccurs="0">
   <classRef key="model.descLike"
    minOccurs="1" maxOccurs="unbounded"/>
   <sequence minOccurs="0"
    maxOccurs="unbounded">
    <classRef key="model.identSynonyms"
     minOccurs="1" maxOccurs="1"/>
    <classRef key="model.descLike"
     minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
   <elementRef key="remarks" minOccurs="0"
    maxOccurs="unbounded"/>
  </sequence>
  <elementRef key="paramList" minOccurs="0"
   maxOccurs="1"/>
 </sequence>
</content>
    
Schema Declaration
element valItem
{
   tei_att.global.attributes,
   tei_att.combinable.attributes,
   attribute ident { text },
   (
      tei_model.identSynonyms*,
      (
         (
            tei_model.descLike+,
            ( ( tei_model.identSynonyms, tei_model.descLike* )* ),
            tei_remarks*
         )?
      ),
      tei_paramList?
   )
}

1.307. <valList>

<valList> (value list) contains one or more <valItem> elements defining possible values. [23.5.3. Attribute List Specification]
Moduletagdocs
Attributes
typespecifies the extensibility of the list of values specified.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
closed
only the values specified are permitted.
semi
(semi-open) all the values specified should be supported, but other values are legal and software should have appropriate fallback processing for them.
open
the values specified are sample values only.[Default]
Contained by
May contain
tagdocs: valItem
Example
<valList type="closed">  <valItem ident="req">   <gloss>required</gloss>  </valItem>  <valItem ident="rec">   <gloss>recommended</gloss>  </valItem>  <valItem ident="opt">   <gloss>optional</gloss>  </valItem> </valList>
Content model
<content>
 <elementRef key="valItem" minOccurs="0"
  maxOccurs="unbounded"/>
</content>
    
Schema Declaration
element valList
{
   tei_att.global.attributes,
   tei_att.combinable.attributes,
   attribute type { "closed" | "semi" | "open" }?,
   tei_valItem*
}

1.308. <xenoData>

<xenoData> (non-TEI metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata]
Moduleheader
Attributes
Member of
Contained by
header: teiHeader
May containANY
ExampleThis example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#. Note: The about attribute on the <rdf:Description> in this example gives a URI indicating the resource to which the metadata contained therein refer. The <rdf:Description> in the second <xenoData> block has a blank about, meaning it is pointing at the current document, so the RDF is about the document within which it is contained, i.e. the TEI document containing the <xenoData> block. Similarly, any kind of relative URI may be used, including fragment identifiers (see [[undefined SG-id]]). Do note, however, that if the contents of the <xenoData> block are to be extracted and used elsewhere, any relative URIs will have to be resolved accordingly.
<xenoData    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">  <rdf:RDF>   <rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">    <dc:title>The description of a new world, called the blazing-world</dc:title>    <dc:creator>The Duchess of Newcastle</dc:creator>    <dc:date>1667</dc:date>    <dc:identifier>British Library, 8407.h.10</dc:identifier>    <dc:subject>utopian fiction</dc:subject>   </rdf:Description>  </rdf:RDF> </xenoData> <xenoData>  <rdf:RDF>   <rdf:Description rdf:about="">    <dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>    <dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>    <dc:publisher>Women Writers Project</dc:publisher>    <dc:date>2002-02-12</dc:date>    <dc:subject>utopian fiction</dc:subject>   </rdf:Description>  </rdf:RDF> </xenoData>
ExampleIn this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.
<xenoData    xmlns:cc="http://web.resource.org/cc/"    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">  <rdf:RDF>   <cc:Work rdf:about="">    <dc:title>Applied Software Project Management - review</dc:title>    <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>    <dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/>   </cc:Work>   <cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">    <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>    <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>    <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>    <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>    <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>    <cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/>   </cc:License>  </rdf:RDF> </xenoData>
ExampleIn this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.
<xenoData    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/">  <oai_dc:dc>   <dc:title>The colonial despatches of Vancouver Island and British      Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.      Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>   <dc:date>1858-11-12</dc:date>   <dc:creator>Trevelyan</dc:creator>   <dc:publisher>University of Victoria Humanities Computing and Media      Centre, and UVic Libraries</dc:publisher>   <dc:type>InteractiveResource</dc:type>   <dc:format>application/xhtml+xml</dc:format>   <dc:type>text</dc:type>   <dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>   <dc:rights>This document is licensed under a Creative Commons …</dc:rights>   <dc:language>(SCHEME=ISO639) en</dc:language>   <dc:source>Transcribed from microfilm and/or original documents, and      marked up in TEI P5 XML. The interactive XHTML resource is generated      from the XHTML using XQuery and XSLT.</dc:source>   <dc:source>repository: CO</dc:source>   <dc:source>coNumber: 60</dc:source>   <dc:source>coVol: 2</dc:source>   <dc:source>page: 291</dc:source>   <dc:source>coRegistration: 11566</dc:source>   <dc:source>received: received 13 November</dc:source>   <dc:subject>Trevelyan, Sir Charles Edward</dc:subject>   <dc:subject>Merivale, Herman</dc:subject>   <dc:subject>Elliot, T. Frederick</dc:subject>   <dc:subject>Moody, Colonel Richard Clement</dc:subject>   <dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>   <dc:subject>Jadis, Vane</dc:subject>   <dc:subject>Carnarvon, Earl</dc:subject>   <dc:subject>British Columbia</dc:subject>   <dc:description>British Columbia correspondence: Public Offices      document (normally correspondence between government      departments)</dc:description>  </oai_dc:dc> </xenoData>
ExampleIn this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.
<xenoData    xmlns:mods="http://www.loc.gov/mods/v3">  <mods:mods>   <mods:titleInfo>    <mods:title>Academic adaptation and cross-cultural        learning experiences of Chinese students at American        universities</mods:title>    <mods:subTitle>a narrative inquiry</mods:subTitle>   </mods:titleInfo>   <mods:name type="personal"    authority="local">    <mods:namePart/>    <mods:role>     <mods:roleTerm authority="marcrelator"      type="text">Author</mods:roleTerm>    </mods:role>    <mods:affiliation>Northeastern University</mods:affiliation>    <mods:namePart type="given">Hong</mods:namePart>    <mods:namePart type="family">Zhang</mods:namePart>   </mods:name>   <mods:name type="personal"    authority="local">    <mods:namePart/>    <mods:role>     <mods:roleTerm authority="local"      type="text">Advisor</mods:roleTerm>    </mods:role>    <mods:namePart type="given">Liliana</mods:namePart>    <mods:namePart type="family">Meneses</mods:namePart>   </mods:name>    <!-- ... -->   <mods:typeOfResource>text</mods:typeOfResource>   <mods:genre>doctoral theses</mods:genre>   <mods:originInfo>    <mods:place>     <mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm>    </mods:place>    <mods:publisher>Northeastern University</mods:publisher>    <mods:copyrightDate encoding="w3cdtf"     keyDate="yes">2013</mods:copyrightDate>   </mods:originInfo>   <mods:language>    <mods:languageTerm authority="iso639-2b"     type="code">eng</mods:languageTerm>   </mods:language>   <mods:physicalDescription>    <mods:form authority="marcform">electronic</mods:form>    <mods:digitalOrigin>born digital</mods:digitalOrigin>   </mods:physicalDescription> <!-- ... -->  </mods:mods> </xenoData>
ExampleThis example shows GeoJSON embedded in <xenoData>. Note that JSON does not permit newlines inside string values. These must be escaped as \n. To avoid the accidental insertion of newlines by software, the use of xml:space is recommended. Blocks of JSON should be wrapped in CDATA sections, as they may contain characters illegal in XML.
<xenoData xml:space="preserve"> <![CDATA[ {     "features": [         {             "geometry": {                 "type": "Point",                 "coordinates": [                     68.388483,                     33.498616                 ]             },             "type": "Feature",             "id": "darmc-location-19727",             "properties": {                 "snippet": "Unknown; 330 BC - AD 300",                 "link": "https://pleiades.stoa.org/places/59694/darmc-location-19727",                 "description": "5M scale point location",                 "location_precision": "precise",                 "title": "DARMC location 19727"             }         }     ],     "id": "59694",     "subject": [         "dare:ancient=1",         "dare:feature=settlement",         "dare:major=0"     ],     "title": "Arachosiorum Oppidum/Alexandria",     "provenance": "Barrington Atlas: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",     "placeTypeURIs": [         "https://pleiades.stoa.org/vocabularies/place-types/settlement"     ],     "details": "<p>The Barrington Atlas Directory notes: Kalat-e-Ghilzai? AFG</p>",     "@context": {         "snippet": "dcterms:abstract",         "rights": "dcterms:rights",         "description": "dcterms:description",         "title": "dcterms:title",         "dcterms": "http://purl.org/dc/terms/",         "subject": "dcterms:subject",         "uri": "@id",         "created": "dcterms:created"     },     "review_state": "published",     "type": "FeatureCollection",     "description": "An ancient place, cited: BAtlas 6 B3 Arachosiorum Oppidum/Alexandria",     "reprPoint": [         68.388483,         33.498616     ],     "placeTypes": [         "settlement"     ],     "bbox": [         68.388483,         33.498616,         68.388483,         33.498616     ],     "rights": "Copyright © The Contributors. Sharing and remixing permitted under CC-BY.",     "created": "2010-09-23T04:31:55Z",     "uri": "https://pleiades.stoa.org/places/59694",     "creators": [         {             "username": null,             "name": "M.U. Erdosy"         }     ],     "@type": "Place" } ]]> </xenoData>
Note: the example above has been trimmed for legibility. The original may be found linked from Arachosiorum Oppidum/Alexandria. The contributors, listed per the license terms, are R. Talbert, Jeffrey Becker, W. Röllig, Tom Elliott, H. Kopp, DARMC, Sean Gillies, B. Siewert-Mayer, Francis Deblauwe, and Eric Kansa.
Content model
<content>
 <alternate>
  <textNode/>
  <anyElement/>
 </alternate>
</content>
    
Schema Declaration
element xenoData
{
   tei_att.global.attributes,
   tei_att.declarable.attributes,
   tei_att.typed.attributes,
   ( text | anyElement_xenoData_1 )
}

2. Model classes

2.2. model.addressLike

model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure]
Moduletei
Used by
Membersaddress affiliation email

2.3. model.applicationLike

model.applicationLike groups elements used to record application-specific information about a document in its header.
Moduletei
Used by
Membersapplication

2.4. model.attributable

model.attributable groups elements that contain a word or phrase that can be attributed to a source. [3.3.3. Quotation 4.3.2. Floating Texts]
Moduletei
Used by
Membersmodel.quoteLike[cit quote] floatingText said

2.5. model.availabilityPart

model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Memberslicence

2.6. model.biblLike

2.8. model.choicePart

model.choicePart groups elements (other than <choice> itself) which can be used within a <choice> alternation. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersabbr corr expan orig reg sic unclear

2.9. model.common

2.10. model.contentPart

model.contentPart groups elements which may appear as part of the content element. [23.5.1. Defining Content Models]
Moduletagdocs
Used by
Membersalternate anyElement classRef dataRef elementRef empty macroRef sequence textNode

2.12. model.correspContextPart

model.correspContextPart groups elements which may appear as part of the correspContext element
Moduletei
Used by
Membersmodel.pLike[p] model.ptrLike[listRef ptr ref] note noteGrp

2.13. model.correspDescPart

model.correspDescPart groups together metadata elements for describing correspondence
Moduletei
Used by
MemberscorrespAction correspContext note noteGrp

2.14. model.dateLike

model.dateLike groups elements containing temporal expressions. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Used by
Membersdate time

2.15. model.descLike

2.16. model.describedResource

model.describedResource groups elements which contain the content of a digital resource and its metadata; these elements may serve as the outermost or ‘root’ element of a TEI-conformant document [1.3. The TEI Class System]
Moduletei
Used by
MembersTEI teiCorpus

2.17. model.div1Like

model.div1Like groups top-level structural divisions.
Moduletei
Used by
Membersdiv1

2.18. model.div2Like

model.div2Like groups second-level structural divisions.
Moduletei
Used by
Membersdiv2

2.19. model.div3Like

model.div3Like groups third-level structural divisions.
Moduletei
Used by
Membersdiv3

2.20. model.div4Like

model.div4Like groups fourth-level structural divisions.
Moduletei
Used by
Membersdiv4

2.21. model.div5Like

model.div5Like groups fifth-level structural divisions.
Moduletei
Used by
Membersdiv5

2.22. model.div6Like

model.div6Like groups sixth-level structural divisions.
Moduletei
Used by
Membersdiv6

2.23. model.div7Like

model.div7Like groups seventh-level structural divisions.
Moduletei
Used by
Membersdiv7

2.24. model.divBottom

2.25. model.divBottomPart

model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages]
Moduletei
Used by
Memberscloser postscript signed trailer

2.26. model.divGenLike

model.divGenLike groups elements used to represent a structural division which is generated rather than explicitly present in the source.
Moduletei
Used by
MembersdivGen

2.27. model.divLike

model.divLike groups elements used to represent un-numbered generic structural divisions.
Moduletei
Used by
Membersdiv

2.28. model.divPart

model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System]
Moduletei
Used by
Membersmodel.lLike[l] model.pLike[p] lg sp
Note

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

2.29. model.divTop

2.30. model.divTopPart

model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages]
Moduletei
Used by
Membersmodel.headLike[head] opener signed

2.31. model.divWrapper

model.divWrapper groups elements which can appear at either top or bottom of a textual division. [4.2. Elements Common to All Divisions]
Moduletei
Used by
Membersargument byline dateline docAuthor docDate epigraph meeting salute

2.32. model.editorialDeclPart

model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times.
Moduletei
Used by
Memberscorrection hyphenation interpretation normalization punctuation quotation segmentation stdVals

2.33. model.egLike

model.egLike groups elements containing examples or illustrations. [23.1.1. Phrase Level Terms]
Moduletei
Used by
Memberseg egXML

2.34. model.emphLike

model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Memberscode distinct emph foreign gloss ident mentioned soCalled term title

2.35. model.encodingDescPart

model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times.
Moduletei
Used by
MembersappInfo classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl schemaRef schemaSpec styleDefDecl tagsDecl unitDecl

2.36. model.eventLike

model.eventLike groups elements which describe events.
Moduletei
Used by
Membersevent listEvent

2.37. model.frontPart

model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ]
Moduletei
Used by
Membersmodel.frontPart.drama divGen listBibl schemaSpec titlePage

2.39. model.global.edit

model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System]
Moduletei
Used by
Membersellipsis gap

2.40. model.global.meta

model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System]
Moduletei
Used by
Membersindex
Note

Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text.

2.41. model.graphicLike

model.graphicLike groups elements containing images, formulae, and similar objects. [3.10. Graphics and Other Non-textual Components]
Moduletei
Used by
MembersbinaryObject graphic media

2.42. model.headLike

model.headLike groups elements used to provide a title or heading at the start of a text division.
Moduletei
Used by
Membershead

2.43. model.hiLike

model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membershi q

2.44. model.highlighted

model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation]
Moduletei
Used by
Membersmodel.emphLike[code distinct emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q]

2.45. model.identEquiv

model.identEquiv groups elements which provide an equivalent value to the identity of their parent element, either as a formal construct or in natural language.
Moduletei
Used by
Membersequiv gloss

2.46. model.identSynonyms

model.identSynonyms groups elements which provide an explanation, equivalency, or alternative name for a markup construct.
Moduletei
Used by
Membersmodel.identEquiv[equiv gloss] altIdent

2.47. model.imprintPart

model.imprintPart groups the bibliographic elements which occur inside imprints. [3.12. Bibliographic Citations and References]
Moduletei
Used by
MembersbiblScope distributor pubPlace publisher

2.49. model.lLike

model.lLike groups elements representing metrical components such as verse lines.
Moduletei
Used by
Membersl

2.50. model.labelLike

model.labelLike groups elements used to gloss or explain other parts of a document.
Moduletei
Used by
Membersdesc label

2.52. model.listLike

model.listLike groups list-like elements. [3.8. Lists]
Moduletei
Used by
Memberslist listEvent listNym listObject listOrg listPerson listPlace listRelation

2.53. model.measureLike

model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.6.3. Numbers and Measures]
Moduletei
Used by
Membersgeo measure measureGrp num unit

2.54. model.milestoneLike

model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.11.3. Milestone Elements]
Moduletei
Used by
Memberscb gb lb milestone pb

2.55. model.nameLike

model.nameLike groups elements which name or refer to a person, place, or organization.
Moduletei
Used by
Membersmodel.nameLike.agent[name orgName persName] model.offsetLike[geogFeat offset] model.persNamePart[addName forename genName nameLink persPronouns roleName surname] model.placeStateLike[model.placeNamePart[bloc country district geogName placeName region settlement] climate location population state terrain trait] eventName idno objectName rs
Note

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

2.56. model.nameLike.agent

model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.6. Names, Numbers, Dates, Abbreviations, and Addresses]
Moduletei
Used by
Membersname orgName persName
Note

This class is used in the content model of elements which reference names of people or organizations.

2.57. model.noteLike

model.noteLike groups globally-available note-like elements. [3.9. Notes, Annotation, and Indexing]
Moduletei
Used by
Membersnote noteGrp

2.58. model.objectLike

model.objectLike groups elements which describe objects.
Moduletei
Used by
MemberslistObject object

2.59. model.oddDecl

model.oddDecl groups elements which generate declarations in some markup language in ODD documents.
Moduletei
Used by
MembersclassSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec outputRendition specGrp specGrpRef

2.60. model.oddRef

model.oddRef groups elements which reference declarations in some markup language in ODD documents.
Moduletei
Used by
MembersclassRef dataRef elementRef macroRef moduleRef

2.61. model.offsetLike

model.offsetLike groups elements which can appear only as part of a place name. [14.2.3. Place Names]
Moduletei
Used by
MembersgeogFeat offset

2.62. model.orgPart

model.orgPart groups elements which form part of the description of an organization.
Moduletei
Used by
Membersmodel.eventLike[event listEvent] listOrg listPerson listPlace

2.64. model.pLike.front

model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages]
Moduletei
Used by
Membersargument byline dateline docAuthor docDate docEdition docImprint docTitle epigraph head titlePart

2.66. model.pPart.edit

model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersmodel.pPart.editorial[abbr choice expan] model.pPart.transcriptional[add corr del orig reg sic unclear]

2.67. model.pPart.editorial

model.pPart.editorial groups phrase-level elements for simple editorial interventions that may be useful both in transcribing and in authoring. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersabbr choice expan

2.68. model.pPart.transcriptional

model.pPart.transcriptional groups phrase-level elements used for editorial transcription of pre-existing source materials. [3.5. Simple Editorial Changes]
Moduletei
Used by
Membersadd corr del orig reg sic unclear

2.69. model.paraPart

model.paraPart groups elements that may appear in paragraphs and similar elements [3.1. Paragraphs]
Moduletei
Used by
Membersmodel.gLike model.global[model.global.edit[ellipsis gap] model.global.meta[index] model.milestoneLike[cb gb lb milestone pb] model.noteLike[note noteGrp]] model.inter[model.attributable[model.quoteLike[cit quote] floatingText said] model.biblLike[bibl biblFull biblStruct listBibl] model.egLike[eg egXML] model.labelLike[desc label] model.listLike[list listEvent listNym listObject listOrg listPerson listPlace listRelation] model.oddDecl[classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec outputRendition specGrp specGrpRef] model.stageLike[stage]] model.lLike[l] model.phrase[model.graphicLike[binaryObject graphic media] model.highlighted[model.emphLike[code distinct emph foreign gloss ident mentioned soCalled term title] model.hiLike[hi q]] model.lPart model.pPart.data[model.addressLike[address affiliation email] model.dateLike[date time] model.measureLike[geo measure measureGrp num unit] model.nameLike[model.nameLike.agent[name orgName persName] model.offsetLike[geogFeat offset] model.persNamePart[addName forename genName nameLink persPronouns roleName surname] model.placeStateLike[model.placeNamePart[bloc country district geogName placeName region settlement] climate location population state terrain trait] eventName idno objectName rs]] model.pPart.edit[model.pPart.editorial[abbr choice expan] model.pPart.transcriptional[add corr del orig reg sic unclear]] model.pPart.msdesc model.phrase.xml[att gi tag val] model.ptrLike[listRef ptr ref] model.segLike model.specDescLike[specDesc specList] ruby] lg

2.70. model.persNamePart

model.persNamePart groups elements which form part of a personal name. [14.2.1. Personal Names]
Modulenamesdates
Used by
MembersaddName forename genName nameLink persPronouns roleName surname

2.71. model.persStateLike

model.persStateLike groups elements describing changeable characteristics of a person which have a definite duration, for example occupation, residence, or name.
Moduletei
Used by
Membersaffiliation age education faith floruit gender langKnowledge nationality occupation persName persPronouns persona residence sex socecStatus state trait
Note

These characteristics of an individual are typically a consequence of their own action or that of others.

2.72. model.personLike

model.personLike groups elements which provide information about people and their relationships.
Moduletei
Used by
Membersorg person personGrp

2.75. model.phrase.xml

model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [23. Documentation Elements]
Moduletei
Used by
Membersatt gi tag val

2.76. model.placeLike

model.placeLike groups elements used to provide information about places and their relationships.
Moduletei
Used by
Membersplace

2.77. model.placeNamePart

model.placeNamePart groups elements which form part of a place name. [14.2.3. Place Names]
Moduletei
Used by
Membersbloc country district geogName placeName region settlement

2.78. model.placeStateLike

model.placeStateLike groups elements which describe changing states of a place.
Moduletei
Used by
Membersmodel.placeNamePart[bloc country district geogName placeName region settlement] climate location population state terrain trait

2.79. model.profileDescPart

model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times.
Moduletei
Used by
Membersabstract calendarDesc correspDesc creation langUsage textClass

2.81. model.publicationStmtPart.agency

model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Membersauthority distributor publisher
Note

The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.

See also model.publicationStmtPart.detail.

2.82. model.publicationStmtPart.detail

model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.]
Moduletei
Used by
Membersmodel.ptrLike[listRef ptr ref] address availability date idno pubPlace
Note

A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.

See also model.publicationStmtPart.agency.

2.83. model.quoteLike

model.quoteLike groups elements used to directly contain quotations.
Moduletei
Used by
Memberscit quote

2.84. model.resource

model.resource groups separate elements which constitute the content of a digital resource, as opposed to its metadata. [1.3. The TEI Class System]
Moduletei
Used by
Memberstext

2.85. model.respLike

model.respLike groups elements which are used to indicate intellectual or other significant responsibility, for example within a bibliographic element.
Moduletei
Used by
Membersauthor editor funder meeting principal respStmt sponsor

2.86. model.specDescLike

model.specDescLike groups elements for referring to specification elements. [23. Documentation Elements]
Moduletei
Used by
MembersspecDesc specList

2.87. model.stageLike

model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text]
Moduletei
Used by
Membersstage
Note

Stage directions are members of class inter: that is, they can appear between or within component-level elements.

2.88. model.teiHeaderPart

model.teiHeaderPart groups high level elements which may appear more than once in a TEI header.
Moduletei
Used by
MembersencodingDesc profileDesc xenoData

2.89. model.titlepagePart

model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages]
Moduletei
Used by
Membersargument binaryObject byline docAuthor docDate docEdition docImprint docTitle epigraph graphic imprimatur titlePart

3. Attribute classes

3.1. att.anchoring

att.anchoring (anchoring) provides attributes for use on annotations, e.g. notes and groups of notes describing the existence and position of an anchor for annotations.
Moduletei
Membersnote noteGrp
Attributes
anchored(anchored) indicates whether the copy text shows the exact place of reference for the note.
StatusOptional
Datatypeteidata.truthValue
Defaulttrue
Note

In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.

targetEnd(target end) points to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 17.2.4.6. range().

Example
<p>(...) tamen reuerendos dominos archiepiscopum et canonicos Leopolienses necnon episcopum in duplicibus Quatuortemporibus<anchor xml:id="A55234"/> totaliter expediui...</p> <!-- elsewhere in the document --> <noteGrp targetEnd="#A55234">  <note xml:lang="en"> Quatuor Tempora, so called dry fast days.  </note>  <note xml:lang="pl"> Quatuor Tempora, tzw. Suche dni postne.  </note> </noteGrp>

3.2. att.ascribed

att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Membersatt.ascribed.directed[q said sp stage] change
Attributes
whoindicates the person, or group of people, to whom the element content is ascribed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Hamlet, speeches (<sp>) in the body of the play are linked to <role> elements in the <castList> using the who attribute.
<castItem type="role">  <role xml:id="Barnardo">Bernardo</role> </castItem> <castItem type="role">  <role xml:id="Francisco">Francisco</role>  <roleDesc>a soldier</roleDesc> </castItem> <!-- ... --> <sp who="#Barnardo">  <speaker>Bernardo</speaker>  <l n="1">Who's there?</l> </sp> <sp who="#Francisco">  <speaker>Francisco</speaker>  <l n="2">Nay, answer me: stand, and unfold yourself.</l> </sp>
Note

For transcribed speech, this will typically identify a participant or participant group; in other contexts, it will point to any identified <person> element.

3.3. att.ascribed.directed

att.ascribed.directed provides attributes for elements representing speech or action that can be directed at a group or individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts]
Moduletei
Membersq said sp stage
Attributes
toWhomindicates the person, or group of people, to whom a speech act or action is directed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
In the following example from Mary Pix's The False Friend, speeches (<sp>) in the body of the play are linked to <castItem> elements in the <castList> using the toWhom attribute, which is used to specify who the speech is directed to. Additionally, the <stage> includes toWhom to indicate the directionality of the action.
<castItem type="role">  <role xml:id="emil">Emilius.</role> </castItem> <castItem type="role">  <role xml:id="lov">Lovisa</role> </castItem> <castItem type="role">  <role xml:id="serv">A servant</role> </castItem> <!-- ... --> <sp who="#emil"  toWhom="#lov">  <speaker>Emil.</speaker>  <l n="1">My love!</l> </sp> <sp who="#lov"  toWhom="#emil">  <speaker>Lov.</speaker>  <l n="2">I have no Witness of my Noble Birth</l>  <stage who="emil"   toWhom="#serv">Pointing to her Woman.</stage>  <l>But that poor helpless wretch——</l> </sp>
Note

To indicate the recipient of written correspondence, use the elements used in section 2.4.6. Correspondence Description, rather than a toWhom attribute.

3.4. att.breaking

att.breaking provides attributes to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.11.3. Milestone Elements]
Moduletei
Memberscb gb lb milestone pb
Attributes
breakindicates whether or not the element bearing this attribute should be considered to mark the end of an orthographic token in the same way as whitespace.
StatusRecommended
Datatypeteidata.enumerated
Sample values include
yes
the element bearing this attribute is considered to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
no
the element bearing this attribute is considered not to mark the end of any adjacent orthographic token irrespective of the presence of any adjacent whitespace
maybe
the encoding does not take any position on this issue.
In the following lines from the Dream of the Rood, linebreaks occur in the middle of the words lāðost and reord-berendum.
<ab> ...eƿesa tome iu icƿæs ȝeƿorden ƿita heardoſt . leodum la<lb break="no"/> ðost ærþan ichim lifes ƿeȝ rihtne ȝerymde reord be<lb break="no"/> rendum hƿæt me þaȝeƿeorðode ƿuldres ealdor ofer... </ab>

3.5. att.cReferencing

att.cReferencing provides attributes that may be used to supply a canonical reference as a means of identifying the target of a pointer.
Moduletei
Membersgloss ptr ref term
Attributes
cRef(canonical reference) specifies the destination of the pointer by supplying a canonical reference expressed using the scheme defined in a <refsDecl> element in the TEI header
StatusOptional
Datatypeteidata.text
Note

The value of cRef should be constructed so that when the algorithm for the resolution of canonical references (described in section 17.2.5. Canonical References) is applied to it the result is a valid URI reference to the intended target.

The <refsDecl> to use may be indicated with the decls attribute.

Currently these Guidelines only provide for a single canonical reference to be encoded on any given <ptr> element.

3.6. att.calendarSystem

att.calendarSystem provides attributes for indicating calendar systems to which a date belongs. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersdate docDate time
Attributes
calendarindicates one or more systems or calendars to which the date represented by the content of this element belongs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@calendar]"> <sch:assert test="string-length( normalize-space(.) ) gt 0"> @calendar indicates one or more systems or calendars to which the date represented by the content of this element belongs, but this <sch:name/> element has no textual content.</sch:assert> </sch:rule>
He was born on <date calendar="#gregorian">Feb. 22, 1732</date> (<date calendar="#julian"  when="1732-02-22">Feb. 11, 1731/32, O.S.</date>).
He was born on <date calendar="#gregorian #julian"  when="1732-02-22">Feb. 22, 1732 (Feb. 11, 1731/32, O.S.)</date>.
Note

Note that the calendar attribute declares the calendar system used to interpret the textual content of an element, as it appears on an original source. It does not modify the interpretation of the normalization attributes provided by att.datable.w3c, att.datable.iso, or att.datable.custom. Attributes from those first two classes are always interpreted as Gregorian or proleptic Gregorian dates, as per the respective standards on which they are based. The calender system used to interpret the last (att.datable.custom) may be specified with datingMethod.

3.7. att.canonical

att.canonical provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. [14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.naming[att.personal[addName eventName forename genName name objectName orgName persName placeName roleName surname] affiliation author birth bloc climate country death district editor education event geogFeat geogName nationality occupation offset population pubPlace region residence rs settlement socecStatus state terrain trait] authority catDesc correspDesc date distributor docAuthor docTitle faith funder meeting object principal publisher relation resp respStmt sponsor term time title unitDecl unitDef
Attributes
keyprovides an externally-defined means of identifying the entity (or entities) being named, using a coded value of some kind.
StatusOptional
Datatypeteidata.text
<author>  <name key="Hugo, Victor (1802-1885)"   ref="http://www.idref.fr/026927608">Victor Hugo</name> </author>
Note

The value may be a unique identifier from a database, or any other externally-defined string identifying the referent. No particular syntax is proposed for the values of the key attribute, since its form will depend entirely on practice within a given project.

ref(reference) provides an explicit means of locating a full definition or identity for the entity being named by means of one or more URIs.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<name ref="http://viaf.org/viaf/109557338"  type="person">Seamus Heaney</name>
Note

The value must point directly to one or more XML elements or other resources by means of one or more URIs, separated by whitespace. If more than one is supplied the implication is that the name identifies several distinct entities.

ExampleIn this contrived example, a canonical reference to the same organisation is provided in four different ways.
<author n="1">  <name ref="http://nzetc.victoria.ac.nz/tm/scholarly/name-427308.html"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="2">  <name ref="nzvn:427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="3">  <name ref="./named_entities.xml#o427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>   <author n="4">  <name key="name-427308"   type="organisation">New Zealand Parliament, Legislative Council</name> </author>
The first presumes the availability of an internet connection and a processor that can resolve a URI (most can). The second requires, in addition, a <prefixDef> that declares how the nzvm prefix should be interpreted. The third does not require an internet connection, but does require that a file named named_entities.xml be in the same directory as the TEI document. The fourth requires that an entire external system for key resolution be available.
Note

The key attribute is more flexible and general-purpose, but its use in interchange requires that documentation about how the key is to be resolved be sent to the recipient of the TEI document. In contrast values of the ref attribute are resolved using the widely accepted protocols for a URI, and thus less documentation, if any, is likely required by the recipient in data interchange.

These guidelines provide no semantic basis or suggested precedence when both key and ref are provided. For this reason simultaneous use of both is not recommended unless documentation explaining the use is provided, probably in an ODD customizaiton, for interchange.

3.8. att.citeStructurePart

att.citeStructurePart provides attributes for selecting particular elements within a document.
Moduleheader
MembersciteData citeStructure
Attributes
use(use) supplies an XPath selection pattern using the syntax defined in [[undefined XSLT3]]. The XPath pattern is relative to the context given in match, which will either be a sibling attribute in the case of <citeStructure> or on the parent <citeStructure> in the case of <citeData>.
StatusRequired
Datatypeteidata.xpath

3.9. att.citing

att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes]
Moduletei
MembersbiblScope citedRange
Attributes
unitidentifies the unit of information conveyed by the element, e.g. columns, pages, volume, entry.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
volume
(volume) the element contains a volume number.
issue
the element contains an issue number, or volume and issue numbers.
page
(page) the element contains a page number or page range.
line
the element contains a line number or line range.
chapter
(chapter) the element contains a chapter indication (number and/or title)
part
the element identifies a part of a book or collection.
column
the element identifies a column.
entry
the element identifies an entry number or label in a list of entries.
fromspecifies the starting point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word
tospecifies the end-point of the range of units indicated by the unit attribute.
StatusOptional
Datatypeteidata.word

3.10. att.cmc

att.cmc (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.
Moduletei
Membersabbr add addName address affiliation argument bibl biblFull biblStruct binaryObject bloc byline cb choice cit climate closer corr country date dateline del desc distinct district docAuthor docDate email emph epigraph expan floatingText foreign forename gap gb genName geo geogFeat geogName gloss graphic head hi idno index l label lb lg list listBibl listEvent listNym listObject listOrg listPerson listPlace listRelation location measure measureGrp media meeting mentioned milestone name nameLink note noteGrp num objectName offset opener orgName orig p pb persName persPronouns placeName population postscript ptr q quote ref reg region roleName rs ruby said salute settlement sic signed soCalled stage state surname term terrain time title trailer trait unclear unit
Attributes
generatedBy(generated by) categorizes how the content of an element was generated in a CMC environment.
StatusOptional
Datatypeteidata.enumerated
Schematron
<sch:rule context="tei:*[@generatedBy]"> <sch:assert test="ancestor-or-self::tei:post">The @generatedBy attribute is for use within a <post> element.</sch:assert> </sch:rule>
Suggested values include:
human
the content was ‘naturally’ typed or spoken by a human user
template
the content was generated after a human user activated a template for its insertion
system
the content was generated by the system, i.e. the CMC environment
bot
the content was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself
unspecified
the content was generated by an unknown or unspecified process
automatic system message in chat: user moves on to another chatroom
<post type="event"  generatedBy="system"  who="#system"  rend="color:blue">  <p>   <name type="nickname"    corresp="#A02">McMike</name> geht    in einen anderen Raum: <name type="roomname">Kreuzfahrt</name>  </p> </post>
automatic system message in chat: user enters a chatroom
<post type="event"  generatedBy="system">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> betritt    den Raum. </p> </post>
automatic system message in chat: user changes his font color
<post type="event"  generatedBy="system"  rend="color:red">  <p>   <name type="nickname"    corresp="#A08">c_bo</name> hat die    Farbe gewechselt.  </p> </post>
An automatic signature of user including an automatic timestamp (Wikipedia discussion, anonymized). The specification of generatedBy at the inner element <signed> is meant to override the specification at the outer element <post>. This is generally possible when the outer generatedBy value is "human".
<post type="standard"  generatedBy="human"  indentLevel="2"  synch="#t00394407"  who="#WU00005582">  <p> Kurze Nachfrage: Die Hieros für den Goldnamen stammen    auch von Beckerath gem. Literatur ? Grüße --</p>  <signed generatedBy="template"   rend="inline">   <gap reason="signatureContent"/>   <time generatedBy="template">18:50, 22. Okt. 2008 (CEST)</time>  </signed> </post>
Wikipedia talk page: user signature
<post type="written"  generatedBy="human"> <!-- ... main content of posting ... -->  <signed generatedBy="template">   <gap reason="signatureContent"/>   <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>  </signed> </post>

3.11. att.combinable

att.combinable provides attributes indicating how multiple references to the same object in a schema should be combined
Moduletagdocs
Membersatt.identified[attDef classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec paramSpec schemaSpec] defaultVal remarks valDesc valItem valList
Attributes
modespecifies the effect of this declaration on its parent object.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
add
this declaration is part of the current definitions.[Default]
delete
the object with the same identifier (and namespace in the case of an element or attribute) as the current one is no longer part of the current definitions
change
this declaration changes the object of the same identifier (and namespace in the case of an element or attribute) in the current definition
replace
this declaration replaces the object with the same identifier (and namespace in the case of an element or attribute) in the current definition.
Note

An ODD processor should handle the values for mode as follows:

add
the object should be created (processing any children in add mode); raise an error if the object has an identifier and an object with the same identifier (and namespace in the case of an element or attribute) already exists.
replace
use this object in preference to any existing object with the same identifier (and namespace in the case of an element or attribute), and ignore any children of that object; process any new children in replace mode
delete
do not process this object or any existing object with the same identifier (and namespace in the case of an element or attribute); the element carrying this attribute must be empty: raise an error if there are any children
change
process this object and its children, replacing only those components of an existing object of the same type with the same identifier (and namespace in case of an element or attribute) that are explicitly specified. This will change only those existing attribute values and child elements that appear both in the original specification and in the new specification. Other children from the original specification will be preserved.

3.12. att.datable

att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersaffiliation age application author birth bloc change climate conversion country creation date death district docDate editor education event eventName faith floruit funder gender geogFeat geogName idno langKnowledge langKnown licence location meeting name nationality objectName occupation offset orgName persName persPronouns placeName population principal region relation residence resp settlement sex socecStatus sponsor state terrain time title trait unitDecl unitDef
Attributes
periodsupplies pointers to one or more definitions of named periods of time (typically <category>s, <date>s or <event>s) within which the datable item is understood to have occurred.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes.

3.13. att.datable.custom

att.datable.custom provides attributes for normalization of elements that contain datable events to a custom dating system (i.e. other than the Gregorian used by W3 and ISO). [14.4. Dates]
Modulenamesdates
Membersatt.datable[affiliation age application author birth bloc change climate conversion country creation date death district docDate editor education event eventName faith floruit funder gender geogFeat geogName idno langKnowledge langKnown licence location meeting name nationality objectName occupation offset orgName persName persPronouns placeName population principal region relation residence resp settlement sex socecStatus sponsor state terrain time title trait unitDecl unitDef]
Attributes
when-customsupplies the value of a date or time in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
The following are examples of custom date or time formats that are not valid ISO or W3C format normalizations, normalized to a different dating system
<p>Alhazen died in Cairo on the <date when="1040-03-06"   when-custom="431-06-12"> 12th day of Jumada t-Tania, 430 AH  </date>.</p> <p>The current world will end at the <date when="2012-12-21"   when-custom="13.0.0.0.0">end of B'ak'tun 13</date>.</p> <p>The Battle of Meggidu (<date when-custom="Thutmose_III:23">23rd year of reign of Thutmose III</date>).</p> <p>Esidorus bixit in pace annos LXX plus minus sub <date when-custom="Ind:4-10-11">die XI mensis Octobris indictione IIII</date> </p>
Not all custom date formulations will have Gregorian equivalents.The when-custom attribute and other custom dating are not constrained to a datatype by the TEI, but individual projects are recommended to regularize and document their dating formats.
notBefore-customspecifies the earliest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
notAfter-customspecifies the latest possible date for the event in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
from-customindicates the starting point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<event xml:id="FIRE1"  datingMethod="#julian"  from-custom="1666-09-02"  to-custom="1666-09-05">  <head>The Great Fire of London</head>  <p>The Great Fire of London burned through a large part    of the city of London.</p> </event>
to-customindicates the ending point of the period in some custom standard form.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
datingPointsupplies a pointer to some location defining a named point in time with reference to which the datable item is understood to have occurred
StatusOptional
Datatypeteidata.pointer
datingMethodsupplies a pointer to a <calendar> element or other means of interpreting the values of the custom dating attributes.
StatusOptional
Datatypeteidata.pointer
Contayning the Originall, Antiquity, Increaſe, Moderne eſtate, and deſcription of that Citie, written in the yeare <date when-custom="1598"  calendar="#julian"  datingMethod="#julian">1598</date>. by Iohn Stow Citizen of London.
In this example, the calendar attribute points to a <calendar> element for the Julian calendar, specifying that the text content of the <date> element is a Julian date, and the datingMethod attribute also points to the Julian calendar to indicate that the content of the when-custom attribute value is Julian too.
<date when="1382-06-28"  when-custom="6890-06-20"  datingMethod="#creationOfWorld"> μηνὶ Ἰουνίου εἰς <num>κ</num> ἔτους <num>ςωϞ</num> </date>
In this example, a date is given in a Mediaeval text measured ‘from the creation of the world’, which is normalized (in when) to the Gregorian date, but is also normalized (in when-custom) to a machine-actionable, numeric version of the date from the Creation.
Note

Note that the datingMethod attribute (unlike calendar defined in att.datable) defines the calendar or dating system to which the date described by the parent element is normalized (i.e. in the when-custom or other X-custom attributes), not the calendar of the original date in the element.

3.14. att.datable.iso

att.datable.iso provides attributes for normalization of elements that contain datable events using the ISO 8601:2004 standard. [3.6.4. Dates and Times 14.4. Dates]
Modulenamesdates
Membersatt.datable[affiliation age application author birth bloc change climate conversion country creation date death district docDate editor education event eventName faith floruit funder gender geogFeat geogName idno langKnowledge langKnown licence location meeting name nationality objectName occupation offset orgName persName persPronouns placeName population principal region relation residence resp settlement sex socecStatus sponsor state terrain time title trait unitDecl unitDef]
Attributes
when-isosupplies the value of a date or time in a standard form.
StatusOptional
Datatypeteidata.temporal.iso
The following are examples of ISO date, time, and date & time formats that are not valid W3C format normalizations.
<date when-iso="1996-09-24T07:25+00">Sept. 24th, 1996 at 3:25 in the morning</date> <date when-iso="1996-09-24T03:25-04">Sept. 24th, 1996 at 3:25 in the morning</date> <time when-iso="1999-01-04T20:42-05">4 Jan 1999 at 8:42 pm</time> <time when-iso="1999-W01-1T20,70-05">4 Jan 1999 at 8:42 pm</time> <date when-iso="2006-05-18T10:03">a few minutes after ten in the morning on Thu 18 May</date> <time when-iso="03:00">3 A.M.</time> <time when-iso="14">around two</time> <time when-iso="15,5">half past three</time>
All of the examples of the when attribute in the att.datable.w3c class are also valid with respect to this attribute.
He likes to be punctual. I said <q>  <time when-iso="12">around noon</time> </q>, and he showed up at <time when-iso="12:00:00">12 O'clock</time> on the dot.
The second occurence of <time> could have been encoded with the when attribute, as 12:00:00 is a valid time with respect to the W3C XML Schema Part 2: Datatypes Second Edition specification. The first occurence could not.
notBefore-isospecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
notAfter-isospecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.iso
from-isoindicates the starting point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
to-isoindicates the ending point of the period in standard form.
StatusOptional
Datatypeteidata.temporal.iso
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by ISO 8601:2004, using the Gregorian calendar.

If both when-iso and dur-iso are specified, the values should be interpreted as indicating a span of time by its starting time (or date) and duration. That is,
<date when-iso="2007-06-01dur-iso="P8D"/>
indicates the same time period as
<date when-iso="2007-06-01/P8D"/>

In providing a ‘regularized’ form, no claim is made that the form in the source text is incorrect; the regularized form is simply that chosen as the main form for purposes of unifying variant forms under a single heading.

3.15. att.datable.w3c

att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.6.4. Dates and Times 14.4. Dates]
Moduletei
Membersatt.datable[affiliation age application author birth bloc change climate conversion country creation date death district docDate editor education event eventName faith floruit funder gender geogFeat geogName idno langKnowledge langKnown licence location meeting name nationality objectName occupation offset orgName persName persPronouns placeName population principal region relation residence resp settlement sex socecStatus sponsor state terrain time title trait unitDecl unitDef]
Attributes
whensupplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Examples of W3C date, time, and date & time formats.
<p>  <date when="1945-10-24">24 Oct 45</date>  <date when="1996-09-24T07:25:00Z">September 24th, 1996 at 3:25 in the morning</date>  <time when="1999-01-04T20:42:00-05:00">Jan 4 1999 at 8 pm</time>  <time when="14:12:38">fourteen twelve and 38 seconds</time>  <date when="1962-10">October of 1962</date>  <date when="--06-12">June 12th</date>  <date when="---01">the first of the month</date>  <date when="--08">August</date>  <date when="2006">MMVI</date>  <date when="0056">AD 56</date>  <date when="-0056">56 BC</date> </p>
This list begins in the year 1632, more precisely on Trinity Sunday, i.e. the Sunday after Pentecost, in that year the <date calendar="#julian"  when="1632-06-06">27th of May (old style)</date>.
<opener>  <dateline>   <placeName>Dorchester, Village,</placeName>   <date when="1828-03-02">March 2d. 1828.</date>  </dateline>  <salute>To    Mrs. Cornell,</salute> Sunday <time when="12:00:00">noon.</time> </opener>
notBeforespecifies the earliest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
notAfterspecifies the latest possible date for the event in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
fromindicates the starting point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
toindicates the ending point of the period in standard form, e.g. yyyy-mm-dd.
StatusOptional
Datatypeteidata.temporal.w3c
Schematron
<sch:rule context="tei:*[@when]"> <sch:report test="@notBefore|@notAfter|@from|@to"  role="nonfatal">The @when attribute cannot be used with any other att.datable.w3c attributes.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@from]"> <sch:report test="@notBefore"  role="nonfatal">The @from and @notBefore attributes cannot be used together.</sch:report> </sch:rule>
Schematron
<sch:rule context="tei:*[@to]"> <sch:report test="@notAfter"  role="nonfatal">The @to and @notAfter attributes cannot be used together.</sch:report> </sch:rule>
Example
<date from="1863-05-28to="1863-06-01">28 May through 1 June 1863</date>
Note

The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.

The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.

Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used.

3.16. att.datcat

att.datcat provides attributes that are used to align XML elements or attributes with the appropriate Data Categories (DCs) defined by an external taxonomy, in this way establishing the identity of information containers and values, and providing means of interpreting them. [10.5.2. Lexical View 19.3. Other Atomic Feature Values]
Moduletei
Memberscategory tagUsage taxonomy
Attributes
datcatprovides a pointer to a definition of, and/or general information about, (a) an information container (element or attribute) or (b) a value of an information container (element content or attribute value), by referencing an external taxonomy or ontology. If valueDatcat is present in the immediate context, this attribute takes on role (a), while valueDatcat performs role (b).
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
valueDatcatprovides a definition of, and/or general information about a value of an information container (element content or attribute value), by reference to an external taxonomy or ontology. Used especially where a contrast with datcat is needed.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
targetDatcatprovides a definition of, and/or general information about, information structure of an object referenced or modeled by the containing element, by reference to an external taxonomy or ontology. This attribute has the characteristics of the datcat attribute, except that it addresses not its containing element, but an object that is being referenced or modeled by its containing element.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
ExampleThe example below presents the TEI encoding of the name-value pair <part of speech, common noun>, where the name (key) ‘part of speech’ is abbreviated as ‘POS’, and the value, ‘common noun’ is symbolized by ‘NN’. The entire name-value pair is encoded by means of the element <f>. In TEI XML, that element acts as the container, labeled with the name attribute. Its contents may be complex or simple. In the case at hand, the content is the symbol ‘NN’.The datcat attribute relates the feature name (i.e., the key) to the data category ‘part of speech’, while the attribute valueDatcat relates the feature value to the data category common noun. Both these data categories should be defined in an external and preferably open reference taxonomy or ontology.
<fs>  <f name="POS"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">   <symbol valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"    value="NN"/>  </f> <!-- ... --> </fs>
‘NN’ is the symbol for common noun used e.g. in the CLAWS-7 tagset defined by the University Centre for Computer Corpus Research on Language at the University of Lancaster. The very same data category used for tagging an early version of the British National Corpus, and coming from the BNC Basic (C5) tagset, uses the symbol ‘NN0’ (rather than ‘NN’). Making these values semantically interoperable would be extremely difficult without a human expert if they were not anchored in a single point of an established reference taxonomy of morphosyntactic data categories. In the case at hand, the string http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545 is both a persistent identifier of the data category in question, as well as a pointer to a shared definition of common noun.While the symbols ‘NN’, ‘NN0’, and many others (often coming from languages other than English) are implicitly members of the container category ‘part of speech’, it is sometimes useful not to rely on such an implicit relationship but rather use an explicit identifier for that data category, to distinguish it from other morphosyntactic data categories, such as gender, tense, etc. For that purpose, the above example uses the datcat attribute to reference a definition of part of speech. The reference taxonomy in this example is the CLARIN Concept Registry.If the feature structure markup exemplified above is to be repeated many times in a single document, it is much more efficient to gather the persistent identifiers in a single place and to only reference them, implicitly or directly, from feature structure markup. The following example is much more concise than the one above and relies on the concepts of feature structure declaration and feature value library, discussed in chapter [[undefined FS]].
<fs>  <f name="POSfVal="#commonNoun"/> <!-- ... --> </fs>
The assumption here is that the relevant feature values are collected in a place that the annotation document in question has access to — preferably, a single document per linguistic resource, for example an <fsdDecl> that is XIncluded as a sibling of <text> or a child of <encodingDesc>; a <taxonomy> available resource-wide (e.g., in a shared header) is also an option.The example below presents an <fvLib> element that collects the relevant feature values (most of them omitted). At the same time, this example shows one way of encoding a tagset, i.e., an established inventory of values of (in the case at hand) morphosyntactic categories.
<fvLib n="POS values">  <symbol xml:id="commonNounvalue="NN"   datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <symbol xml:id="properNounvalue="NP"   datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... --> </fvLib>
Note that these Guidelines do not prescribe a specific choice between datcat and valueDatcat in such cases. The former is the generic way of referencing a data category, whereas the latter is more specific, in that it references a data category that represents a value. The choice between them comes into play where a single element — or a tight element complex, such as the <f>/<symbol> complex illustrated above — make it necessary or useful to distinguish between the container data category and its value.
ExampleIn the context of dictionaries designed with semantic interoperability in mind, the following example ensures that the <pos> element is interpreted as the same information container as in the case of the example of <f name="POS"> above.
<gramGrp>  <pos datcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"   valueDatcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545">NN</pos> </gramGrp>
Efficiency of this type of interoperable markup demands that the references to the particular data categories should best be provided in a single place within the dictionary (or a single place within the project), rather than being repeated inside every entry. For the container elements, this can be achieved at the level of <tagUsage>, although here, the valueDatcat attribute should be used, because it is not the <tagUsage> element that is associated with the relevant data category, but rather the element <pos> (or <case>, etc.) that is described by <tagUsage>:
<tagsDecl partial="true"> <!-- ... -->  <namespace name="http://www.tei-c.org/ns/1.0">   <tagUsage gi="pos"    targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">Contains the part of speech.</tagUsage>   <tagUsage gi="case"    targetDatcat="http://hdl.handle.net/11459/CCR_C-1840_9f4e319c-f233-6c90-9117-7270e215f039">Contains information about the grammatical case that the described form is inflected for.</tagUsage> <!-- ... -->  </namespace> </tagsDecl>
Another possibility is to shorten the URIs by means of the <prefixDef> mechanism, as illustrated below:
<listPrefixDef>  <prefixDef ident="ccrmatchPattern="pos"   replacementPattern="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3"/>  <prefixDef ident="ccrmatchPattern="adj"   replacementPattern="http://hdl.handle.net/11459/CCR_C-1230_23653c21-fca1-edf8-fd7c-3df2d6499157"/> </listPrefixDef> <!-- ... --> <entry> <!--...-->  <form>   <orth>isotope</orth>  </form>  <gramGrp>   <pos datcat="ccr:pos"    valueDatcat="ccr:adj">adj</pos>  </gramGrp> <!--...--> </entry>
This mechanism creates implications that are not always wanted, among others, in the case at hand, suggesting that the identifiers ‘pos’ and ‘adj’ belong to a namespace associated with the CLARIN Concept Repository (CCR), whereas that is solely a shorthand mechanism whose scope is the current resource. Documenting this clearly in the header of the dictionary is therefore advised.Yet another possibility is to associate the information about the relationship between a TEI markup element and the data category that it is intended to model already at the level of modeling the dictionary resource, that is, at the level of the ODD, in the <equiv> element that is a child of <elementSpec> or <attDef>.
ExampleThe <taxonomy> element is a handy tool for encoding taxonomies that are later referenced by att.datcat attributes, but it can also act as an intermediary device, for example holding a fragment of an external taxonomy (or ‘flattening’ an external ontology) that is relevant to the project or document at hand. (It is also imaginable that, for the purpose of the project at hand, the local <taxonomy> element combines vocabularies that originate from more than one external taxonomy or ontology.) In such cases, the <taxonomy> creates a local layer of indirection: the att.datcat attributes internal to the resource may reference the <category> elements stored in the header (as well as the <taxonomy> element itself), whereas these same <category> and <taxonomy> elements use att.datcat attributes to reference the original taxonomy or ontology.
<encodingDesc> <!-- ... -->  <classDecl> <!-- ... -->   <taxonomy xml:id="UD-SYN"    datcat="https://universaldependencies.org/u/dep/index.html">    <desc>     <term>UD syntactic relations</term>    </desc>    <category xml:id="acl"     valueDatcat="https://universaldependencies.org/u/dep/acl.html">     <catDesc>      <term>acl</term>: Clausal modifier of noun (adjectival clause)</catDesc>    </category>    <category xml:id="acl_relcl"     valueDatcat="https://universaldependencies.org/u/dep/acl-relcl.html">     <catDesc>      <term>acl:relcl</term>: relative clause modifier</catDesc>    </category>    <category xml:id="advcl"     valueDatcat="https://universaldependencies.org/u/dep/advcl.html">     <catDesc>      <term>advcl</term>: Adverbial clause modifier</catDesc>    </category> <!-- ... -->   </taxonomy>  </classDecl> </encodingDesc>
The above fragment was excerpted from the GB subset of the ParlaMint project in April 2023, and enriched with att.datcat attributes for the purpose of illustrating the mechanism described here.Note that, in the ideal case, the values of att.datcat attributes should be persistent identifiers, and that the addressing scheme of Universal Dependencies is treated here as persistent for the sake of illustration. Note also that the contrast between datcat used on <taxonomy> on the one hand, and the valueDatcat used on <category> on the other, is not mandatory: both kinds of relations could be encoded by means of the generic datcat attribute, but using the former for the container and the latter for the content is more user-friendly.
ExampleThe targetDatcat attribute is designed to be used in, e.g., feature structure declarations, and is analogous to the targetLang attribute of the att.pointing class, in that it describes the object that is being referenced, rather than the referencing object.
<fDecl name="POS"  targetDatcat="http://hdl.handle.net/11459/CCR_C-396_5a972b93-2294-ab5c-a541-7c344c5f26c3">  <fDescr>part of speech (morphosyntactic category)</fDescr>  <vRange>   <vAlt>    <symbol value="NN"     datcat="http://hdl.handle.net/11459/CCR_C-1256_7ec6083c-23d4-224d-6f94-eecbe6861545"/>    <symbol value="NP"     datcat="http://hdl.handle.net/11459/CCR_C-1371_fbebd9ec-a7f4-9a36-d6e9-88ee16b944ae"/> <!-- ... -->   </vAlt>  </vRange> </fDecl>
Above, the <fDecl> uses targetDatcat, because if it were to use datcat, it would be asserting that it is an instance of the container data category part of speech, whereas it is not — it models a container (<f>) that encodes a part of speech. Note also that it is the <f> that is modeled above, not its values, which are used as direct references to data categories; hence the use of datcat in the <symbol> element.
ExampleThe att.datcat attributes can be used for any sort of taxonomies. The example below illustrates their usefulness for describing usage domain labels in dictionaries on the example of the Diccionario da Lingua Portugueza by António de Morais Silva, retro-digitised in the MORDigital project.
<!-- in the dictionary header --><encodingDesc>  <classDecl>   <taxonomy xml:id="domains"> <!--...-->    <category xml:id="domain.medical_and_health_sciences">     <catDesc xml:lang="en">Medical and Health Sciences</catDesc>     <catDesc xml:lang="pt">Ciências Médicas e da Saúde</catDesc>     <category xml:id="domain.medical_and_health_sciences.medicine"      valueDatcat="https://vocabs.rossio.fcsh.unl.pt/pub/morais_domains/pt/page/0025">      <catDesc xml:lang="en">       <term>Medicine</term>       <gloss> <!--...-->       </gloss>      </catDesc>      <catDesc xml:lang="pt">       <term>Medicina</term>       <gloss> <!--...-->       </gloss>      </catDesc>     </category>    </category> <!--...-->   </taxonomy>  </classDecl> </encodingDesc> <!-- inside an <entry> element: --> <usg type="domain"  valueDatcat="#domain.medical_and_health_sciences.medicine">Med.</usg>
In the Morais dictionary, the relevant domain labels are in the header, getting referenced inside the dictionary, from <usg> elements. The vocabulary used for dictionary-internal labelling is in turn anchored in the MorDigital controlled vocabulary service of the NOVA University of Lisbon – School of Social Sciences and Humanities (NOVA FCSH).
Note

The TEI Abstract Model can be expressed as a hierarchy of attribute-value matrices (AVMs) of various types and of various levels of complexity, nested or grouped in various ways. At the most abstract level, an AVM consists of an information container and the value (contents) of that container.

A simple example of an XML serialization of such structures is, on the one hand, the opening and closing tags that delimit and name the container, and, on the other, the content enclosed by the two tags that constitues the value. An analogous example is an attribute name and the value of that attribute.

In a TEI XML example of two equivalent serializations expressing the name-value pair <part-of-speech,common-noun>, namely <pos>commonNoun</pos> and pos="common-noun", one would classify the element <pos> and the attribute pos as containers (mapping onto the first member of the relevant name-value pair), while the character data content of <pos> or the value of pos would be seen as mapping onto the second member of the pair.

The att.datcat class provides means of addressing the containers and their values, while at the same time providing a way to interpret them in the context of external taxonomies or ontologies. Aligning e.g. both the <pos> element and the pos attribute with the same value of an external reference point (i.e., an entry in an agreed taxonomy) affirms the identity of the concept serialised by both the element container and the attribute container, and optionally provides a definition of that concept (in the case at hand, the concept part of speech).

The value of the att.datcat attributes should be a PID (persistent identifier) that points to a specific — and, ideally, shared — taxonomy or ontology. Among the resources that can, to a lesser or greater extent, be used as inventories of (more or less) standardized linguistic categories are the GOLD ontology, CLARIN CCR, OLiA, or TermWeb's DatCatInfo, and also the Universal Dependencies inventory, on the assumption that its URIs are going to persist. It is imaginable that a project may choose to address a local taxonomy store instead, but this risks losing the advantage of interchangeability with other projects.

Historically, datcat and valueDatcat originate from the (now obsolete) ISO 12620:2009 standard, describing the data model and procedures for a Data Category Registry (DCR). The current version of that standard, ISO 12620-1, does not standardize the serialization of pointers, merely mentioning the TEI att.datcat as an example.

Note that no constraint prevents the occurrence of a combination of att.datcat attributes: the <fDecl> element, which is a natural bearer of the targetDatcat attribute, is an instance of a specific modeling element, and, in principle, could be semantically fixed by an appropriate reference taxonomy of modeling devices.

3.17. att.declarable

att.declarable provides attributes for those elements in the TEI header which may be independently selected by means of the special purpose decls attribute. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersavailability bibl biblFull biblStruct correction correspDesc editorialDecl geoDecl hyphenation interpretation langUsage listBibl listEvent listNym listObject listOrg listPerson listPlace normalization projectDesc punctuation quotation refsDecl samplingDecl segmentation seriesStmt sourceDesc stdVals styleDefDecl textClass xenoData
Attributes
defaultindicates whether or not this element is selected by default when its parent is selected.
StatusOptional
Datatypeteidata.truthValue
Legal values are:
true
This element is selected if its parent is selected
false
This element can only be selected explicitly, unless it is the only one of its kind, in which case it is selected if its parent is selected.[Default]
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text. Only one element of a particular type may have a default attribute with a value of true.

3.18. att.declaring

att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [16.3. Associating Contextual Information with a Text]
Moduletei
Membersback body div div1 div2 div3 div4 div5 div6 div7 floatingText front geo gloss graphic group lg media object p ptr ref term text
Attributes
decls(declarations) identifies one or more declarable elements within the header, which are understood to apply to the element bearing this attribute and its content.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 16.3. Associating Contextual Information with a Text.

3.19. att.deprecated

att.deprecated provides attributes indicating how a deprecated feature will be treated in future releases.
Moduletagdocs
Membersatt.combinable[att.identified[attDef classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec paramSpec schemaSpec] defaultVal remarks valDesc valItem valList]
Attributes
validUntilprovides a date before which the construct being defined will not be removed.
StatusOptional
Datatypedate
Schematron
<sch:rule context="tei:*[@validUntil]"> <sch:let name="advance_warning_period"  value="current-date() + xs:dayTimeDuration('P60D')"/> <sch:let name="me_phrase"  value="if (@ident) then concat('The ', @ident ) else concat('This ', local-name(.), ' of ', ancestor::tei:*[@ident][1]/@ident )"/> <sch:assert test="@validUntil cast as xs:date ge current-date()">  <sch:value-of select="concat( $me_phrase, ' construct is outdated (as of ', @validUntil, '); ODD processors may ignore it, and its use is no longer supported' )"/> </sch:assert> <sch:assert role="warning"  test="@validUntil cast as xs:date ge $advance_warning_period">  <sch:value-of select="concat( $me_phrase, ' construct becomes outdated on ', @validUntil )"/> </sch:assert> </sch:rule>
Schematron
<sch:rule context="tei:*[@validUntil][ not( self::tei:valDesc | self::tei:valList | self::tei:defaultVal | self::tei:remarks )]"> <sch:assert test="child::tei:desc[ @type eq 'deprecationInfo']"> A deprecated construct should include, whenever possible, an explanation, but this <sch:value-of select="name(.)"/> does not have a child <desc type="deprecationInfo"></sch:assert> </sch:rule>
Note

The value of this attribute should represent a date (in standard yyyy-mm-dd format) which is later than the date on which the attribute is added to an ODD. Technically, this attribute asserts only the intent to leave a construct in future releases of the markup language being defined up to at least the specified date, and makes no assertion about what happens past that date. In practice, the expectation is that the construct will be removed from future releases of the markup language being defined sometime shortly after the validUntil date.

An ODD processor will typically not process a specification element which has a validUntil date that is in the past. An ODD processor will typically warn users about constructs which have a validUntil date that is in the future. E.g., the documentation for such a construct might include the phrase warning: deprecated in red.

3.20. att.dimensions

att.dimensions provides attributes for describing the size of physical objects.
Moduletei
Membersadd age birth date death del ellipsis floruit gap geogFeat offset population state time trait unclear
Attributes
unitnames the unit used for the measurement
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
cm
(centimetres)
mm
(millimetres)
in
(inches)
line
lines of text
char
(characters) characters of text
quantityspecifies the length in the units specified
StatusOptional
Datatypeteidata.numeric
extentindicates the size of the object concerned using a project-specific vocabulary combining quantity and units in a single string of words.
StatusOptional
Datatypeteidata.text
<gap extent="5 words"/>
<height extent="half the page"/>
precisioncharacterizes the precision of the values specified by the other attributes.
StatusOptional
Datatypeteidata.certainty
scopewhere the measurement summarizes more than one observation, specifies the applicability of this measurement.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
all
measurement applies to all instances.
most
measurement applies to most of the instances inspected.
range
measurement applies to only the specified range of instances.

3.21. att.divLike

att.divLike provides attributes common to all elements which behave in the same way as divisions. [4. Default Text Structure]
Moduletei
Membersdiv div1 div2 div3 div4 div5 div6 div7 lg
Attributes
org(organization) specifies how the content of the division is organized.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
composite
no claim is made about the sequence in which the immediate contents of this division are to be processed, or their inter-relationships.
uniform
the immediate contents of this element are regarded as forming a logical unit, to be processed in sequence.[Default]
sampleindicates whether this division is a sample of the original source and if so, from which part.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
initial
division lacks material present at end in source.
medial
division lacks material at start and end.
final
division lacks material at start.
unknown
position of sampled material within original unknown.
complete
division is not a sample.[Default]

3.22. att.docStatus

att.docStatus provides attributes for use on metadata elements describing the status of a document.
Moduletei
Membersbibl biblFull biblStruct change object revisionDesc schemaSpec
Attributes
statusdescribes the status of a document either currently or, when associated with a dated element, at the time indicated.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
approved
candidate
cleared
deprecated
draft
[Default]
embargoed
expired
frozen
galley
proposed
published
recommendation
submitted
unfinished
withdrawn
Example
<revisionDesc status="published">  <change when="2010-10-21"   status="published"/>  <change when="2010-10-02status="cleared"/>  <change when="2010-08-02"   status="embargoed"/>  <change when="2010-05-01status="frozen"   who="#MSM"/>  <change when="2010-03-01status="draft"   who="#LB"/> </revisionDesc>

3.23. att.editLike

att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.5. Simple Editorial Changes 11.3.1. Origination 14.3.2. The Person Element 12.3.1.1. Core Elements for Transcriptional Work]
Moduletei
Membersatt.transcriptional[add del rt] affiliation age birth climate corr date death education event eventName expan faith floruit gap gender geogFeat geogName langKnowledge langKnown location name nationality objectName occupation offset org orgName persName persPronouns person persona place placeName population reg relation residence sex socecStatus state terrain time trait unclear
Attributes
evidenceindicates the nature of the evidence supporting the reliability or accuracy of the intervention or interpretation.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
internal
there is internal evidence to support the intervention.
external
there is external evidence to support the intervention.
conjecture
the intervention or interpretation has been made by the editor, cataloguer, or scholar on the basis of their expertise.
instantindicates whether this is an instant revision or not.
StatusOptional
Datatypeteidata.xTruthValue
Defaultfalse
Note

The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc.

Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned.

3.24. att.edition

att.edition provides attributes identifying the source edition from which some encoded feature derives.
Moduletei
Memberscb gb lb milestone pb refState
Attributes
ed(edition) supplies a sigil or other arbitrary identifier for the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
edRef(edition reference) provides a pointer to the source edition in which the associated feature (for example, a page, column, or line break) occurs at this point in the text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Example
<l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l> <l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l> <l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l>
Example
<listBibl>  <bibl xml:id="stapledon1937">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>  </bibl>  <bibl xml:id="stapledon1968">   <author>Olaf Stapledon</author>,  <title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>  </bibl> </listBibl> <!-- ... --> <p>Looking into the future aeons from the supreme moment of the cosmos, I saw the populations still with all their strength maintaining the<pb n="411edRef="#stapledon1968"/>essentials of their ancient culture, still living their personal lives in zest and endless novelty of action, … I saw myself still preserving, though with increasing difficulty, my lucid con-<pb n="291edRef="#stapledon1937"/>sciousness;</p>

3.25. att.formula

att.formula provides attributes for defining a mathematical formula. [2.3.9. The Unit Declaration]
Moduletei
Membersconversion
Attributes
formulaA formula is provided to describe a mathematical calculation such as a conversion between measurement systems.
StatusOptional
Datatypeteidata.xpath
Example
<encodingDesc>  <unitDecl>   <unitDef xml:id="stadiumtype="linear">    <label>stadium</label>    <placeName ref="#rome"/>    <conversion fromUnit="#pes"     toUnit="#stadiumformula="$fromUnit * 625"/>    <desc>The stadium was a Roman unit of linear measurement equivalent to 625 pedes, or Roman feet.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<encodingDesc>  <unitDecl>   <unitDef xml:id="wmwtype="power">    <label>whatmeworry</label>    <conversion fromUnit="#hpk"     toUnit="#wmwformula="$fromUnit * 1"/>    <desc>In the Potrzebie system of measures as introduced by Donald Knuth, the whatmeworry unit of power is equivalent to one hah per kovac.</desc>   </unitDef>   <unitDef xml:id="kwmwtype="power">    <label>kilowhatmeworry</label>    <conversion fromUnit="#wmw"     toUnit="#kwmwformula="$fromUnit div 1000"/>    <desc>The kilowhatmeworry is equivalent to 1000 whatmeworries.</desc>   </unitDef>   <unitDef xml:id="aptype="power">    <label>kilowhatmeworry</label>    <conversion fromUnit="#kwmw"     toUnit="#apformula="$fromUnit div 100"/>    <desc>One unit of aeolipower (A.P.) is equivalent to 100 kilowhatmeworries.</desc>   </unitDef>  </unitDecl> </encodingDesc>
Example
<conversion fromUnit="#furlongsPerFortnight"  toUnit="#milesPerHour"  formula="$fromUnit cast as xs:decimal * 0.000372"/>
Example
<conversion fromUnit="#deciday"  toUnit="hour"  formula="$fromUnit cast as xs:decimal * 144 div 60"/>
Note

This attribute class provides formula for use in defining a value used in mathematical calculation. It can be used to store a mathematical operation needed to convert from one system of measurement to another. We use the teidata.xpath datatype to express this value in order to communicate mathematical operations on an XML node or nodes. The $fromUnit variable notation simplifies referencing of the fromUnit attribute on the parent <conversion> element. Note that ‘div’ is required to express the division operator in XPath.

3.26. att.fragmentable

att.fragmentable provides attributes for representing fragmentation of a structural element, typically as a consequence of some overlapping hierarchy.
Moduletei
Membersatt.divLike[div div1 div2 div3 div4 div5 div6 div7 lg] l p
Attributes
partspecifies whether or not its parent element is fragmented in some way, typically by some other overlapping structure: for example a speech which is divided between two or more verse stanzas, a paragraph which is split across a page division, a verse line which is divided between two speakers.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
Y
(yes) the element is fragmented in some (unspecified) respect
N
(no) the element is not fragmented, or no claim is made as to its completeness[Default]
I
(initial) this is the initial part of a fragmented element
M
(medial) this is a medial part of a fragmented element
F
(final) this is the final part of a fragmented element
Note

The values I, M, or F should be used only where it is clear how the element may be reconstituted.

3.27. att.global

att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes]
Moduletei
MembersTEI abbr abstract add addName addrLine address affiliation age altIdent alternate analytic anyElement appInfo application argument att attDef attList attRef author authority availability back bibl biblFull biblScope biblStruct binaryObject birth bloc body byline cRefPattern calendar calendarDesc catDesc catRef category cb change choice cit citeData citeStructure citedRange classCode classDecl classRef classSpec classes climate closer code constraint constraintSpec content conversion corr correction correspAction correspContext correspDesc country creation dataFacet dataRef dataSpec datatype date dateline death defaultVal del desc distinct distributor district div div1 div2 div3 div4 div5 div6 div7 divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl education eg egXML elementRef elementSpec ellipsis email emph empty encodingDesc epigraph equiv event eventName exemplum expan extent faith fileDesc floatingText floruit foreign forename front funder gap gb genName gender geo geoDecl geogFeat geogName gi gloss graphic group handNote head headItem headLabel hi hyphenation ident idno imprimatur imprint index interpretation item keywords l label langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRef listRelation location macroRef macroSpec measure measureGrp media meeting memberOf mentioned milestone model modelGrp modelSequence moduleRef moduleSpec monogr name nameLink namespace nationality normalization note noteGrp notesStmt num nym object objectIdentifier objectName occupation offset opener org orgName orig outputRendition p param paramList paramSpec pb persName persPronouns person personGrp persona place placeName population postBox postCode postscript prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation remarks rendition residence resp respStmt revisionDesc roleName rs rt ruby said salute samplingDecl schemaRef schemaSpec scriptNote segmentation sequence series seriesStmt settlement sex sic signed soCalled socecStatus sourceDesc sp speaker specDesc specGrp specGrpRef specList sponsor stage state stdVals street styleDefDecl surname tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term terrain text textClass textLang textNode time title titlePage titlePart titleStmt trailer trait unclear unit unitDecl unitDef val valDesc valItem valList xenoData
Attributes
xml:id(identifier) provides a unique identifier for the element bearing the attribute.
StatusOptional
DatatypeID
Note

The xml:id attribute may be used to specify a canonical reference for an element; see section 3.11. Reference Systems.

n(number) gives a number (or other label) for an element, which is not necessarily unique within the document.
StatusOptional
Datatypeteidata.text
Note

The value of this attribute is always understood to be a single token, even if it contains space or other punctuation characters, and need not be composed of numbers only. It is typically used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text.

xml:lang(language) indicates the language of the element content using a ‘tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note

The xml:lang value will be inherited from the immediately enclosing element, or from its parent, and so on up the document hierarchy. It is generally good practice to specify xml:lang at the highest appropriate level, noticing that a different default may be needed for the <teiHeader> from that needed for the associated resource element or elements, and that a single TEI document may contain texts in many languages.

Only attributes with free text values (rare in these guidelines) will be in the scope of xml:lang.

The authoritative list of registered language subtags is maintained by IANA and is available at https://www.iana.org/assignments/language-subtag-registry. For a good general overview of the construction of language tags, see https://www.w3.org/International/articles/language-tags/, and for a practical step-by-step guide, see https://www.w3.org/International/questions/qa-choosing-language-tags.en.php.

The value used must conform with BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

xml:baseprovides a base URI reference with which applications can resolve relative URI references into absolute URI references.
StatusOptional
Datatypeteidata.pointer
<div type="bibl">  <head>Selections from <title level="m">The Collected Letters of Robert Southey. Part 1: 1791-1797</title>  </head>  <listBibl xml:base="https://romantic-circles.org/sites/default/files/imported/editions/southey_letters/XML/">   <bibl>    <ref target="letterEEd.26.3.xml">     <title>Robert Southey to Grosvenor Charles Bedford</title>, <date when="1792-04-03">3 April 1792</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.57.xml">     <title>Robert Southey to Anna Seward</title>, <date when="1793-09-18">18 September 1793</date>.    </ref>   </bibl>   <bibl>    <ref target="letterEEd.26.85.xml">     <title>Robert Southey to Robert Lovell</title>, <date from="1794-04-05"      to="1794-04-06">5-6 April, 1794</date>.    </ref>   </bibl>  </listBibl> </div>
xml:spacesignals an intention about how white space should be managed by applications.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
default
signals that the application's default white-space processing modes are acceptable
preserve
indicates the intent that applications preserve all white space
Note

The XML specification provides further guidance on the use of this attribute. Note that many parsers may not handle xml:space correctly.

3.28. att.global.rendition

att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. [1.3.1.1.3. Rendition Indicators]
Moduletei
Membersatt.global[TEI abbr abstract add addName addrLine address affiliation age altIdent alternate analytic anyElement appInfo application argument att attDef attList attRef author authority availability back bibl biblFull biblScope biblStruct binaryObject birth bloc body byline cRefPattern calendar calendarDesc catDesc catRef category cb change choice cit citeData citeStructure citedRange classCode classDecl classRef classSpec classes climate closer code constraint constraintSpec content conversion corr correction correspAction correspContext correspDesc country creation dataFacet dataRef dataSpec datatype date dateline death defaultVal del desc distinct distributor district div div1 div2 div3 div4 div5 div6 div7 divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl education eg egXML elementRef elementSpec ellipsis email emph empty encodingDesc epigraph equiv event eventName exemplum expan extent faith fileDesc floatingText floruit foreign forename front funder gap gb genName gender geo geoDecl geogFeat geogName gi gloss graphic group handNote head headItem headLabel hi hyphenation ident idno imprimatur imprint index interpretation item keywords l label langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRef listRelation location macroRef macroSpec measure measureGrp media meeting memberOf mentioned milestone model modelGrp modelSequence moduleRef moduleSpec monogr name nameLink namespace nationality normalization note noteGrp notesStmt num nym object objectIdentifier objectName occupation offset opener org orgName orig outputRendition p param paramList paramSpec pb persName persPronouns person personGrp persona place placeName population postBox postCode postscript prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation remarks rendition residence resp respStmt revisionDesc roleName rs rt ruby said salute samplingDecl schemaRef schemaSpec scriptNote segmentation sequence series seriesStmt settlement sex sic signed soCalled socecStatus sourceDesc sp speaker specDesc specGrp specGrpRef specList sponsor stage state stdVals street styleDefDecl surname tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term terrain text textClass textLang textNode time title titlePage titlePart titleStmt trailer trait unclear unit unitDecl unitDef val valDesc valItem valList xenoData]
Attributes
rend(rendition) indicates how the element in question was rendered or presented in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
<head rend="align(center) case(allcaps)">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note

These Guidelines make no binding recommendations for the values of the rend attribute; the characteristics of visual presentation vary too much from text to text and the decision to record or ignore individual characteristics varies too much from project to project. Some potentially useful conventions are noted from time to time at appropriate points in the Guidelines. The values of the rend attribute are a set of sequence-indeterminate individual tokens separated by whitespace.

stylecontains an expression in some formal style definition language which defines the rendering or presentation used for this element in the source text
StatusOptional
Datatypeteidata.text
<head style="text-align: center; font-variant: small-caps">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi style="font-variant: normal">New Blazing-World</hi>. </head>
Note

Unlike the attribute values of rend, which uses whitespace as a separator, the style attribute may contain whitespace. This attribute is intended for recording inline stylistic information concerning the source, not any particular output.

The formal language in which values for this attribute are expressed may be specified using the <styleDefDecl> element in the TEI header.

If style and rendition are both present on an element, then style overrides or complements rendition. style should not be used in conjunction with rend, because the latter does not employ a formal style definition language.

renditionpoints to a description of the rendering or presentation used for this element in the source text.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
<head rendition="#ac #sc">  <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/>  <hi rendition="#normal">New Blazing-World</hi>. </head> <!-- elsewhere... --> <rendition xml:id="sc"  scheme="css">font-variant: small-caps</rendition> <rendition xml:id="normal"  scheme="css">font-variant: normal</rendition> <rendition xml:id="ac"  scheme="css">text-align: center</rendition>
Note

The rendition attribute is used in a very similar way to the class attribute defined for XHTML but with the important distinction that its function is to describe the appearance of the source text, not necessarily to determine how that text should be presented on screen or paper.

If rendition is used to refer to a style definition in a formal language like CSS, it is recommended that it not be used in conjunction with rend. Where both rendition and rend are supplied, the latter is understood to override or complement the former.

Each URI provided should indicate a <rendition> element defining the intended rendition in terms of some appropriate style language, as indicated by the scheme attribute.

3.29. att.global.responsibility

att.global.responsibility provides attributes indicating the agent responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [1.3.1.1.4. Sources, certainty, and responsibility 3.5. Simple Editorial Changes 12.3.2.2. Hand, Responsibility, and Certainty Attributes 18.3. Spans and Interpretations 14.1.1. Linking Names and Their Referents]
Moduletei
Membersatt.global[TEI abbr abstract add addName addrLine address affiliation age altIdent alternate analytic anyElement appInfo application argument att attDef attList attRef author authority availability back bibl biblFull biblScope biblStruct binaryObject birth bloc body byline cRefPattern calendar calendarDesc catDesc catRef category cb change choice cit citeData citeStructure citedRange classCode classDecl classRef classSpec classes climate closer code constraint constraintSpec content conversion corr correction correspAction correspContext correspDesc country creation dataFacet dataRef dataSpec datatype date dateline death defaultVal del desc distinct distributor district div div1 div2 div3 div4 div5 div6 div7 divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl education eg egXML elementRef elementSpec ellipsis email emph empty encodingDesc epigraph equiv event eventName exemplum expan extent faith fileDesc floatingText floruit foreign forename front funder gap gb genName gender geo geoDecl geogFeat geogName gi gloss graphic group handNote head headItem headLabel hi hyphenation ident idno imprimatur imprint index interpretation item keywords l label langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRef listRelation location macroRef macroSpec measure measureGrp media meeting memberOf mentioned milestone model modelGrp modelSequence moduleRef moduleSpec monogr name nameLink namespace nationality normalization note noteGrp notesStmt num nym object objectIdentifier objectName occupation offset opener org orgName orig outputRendition p param paramList paramSpec pb persName persPronouns person personGrp persona place placeName population postBox postCode postscript prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation remarks rendition residence resp respStmt revisionDesc roleName rs rt ruby said salute samplingDecl schemaRef schemaSpec scriptNote segmentation sequence series seriesStmt settlement sex sic signed soCalled socecStatus sourceDesc sp speaker specDesc specGrp specGrpRef specList sponsor stage state stdVals street styleDefDecl surname tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term terrain text textClass textLang textNode time title titlePage titlePart titleStmt trailer trait unclear unit unitDecl unitDef val valDesc valItem valList xenoData]
Attributes
cert(certainty) signifies the degree of certainty associated with the intervention or interpretation.
StatusOptional
Datatypeteidata.probCert
resp(responsible party) indicates the agency responsible for the intervention or interpretation, for example an editor or transcriber.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent (<person> or <org>) but to a <respStmt>, <author>, <editor> or similar element which clarifies the exact role played by the agent. Pointing to multiple <respStmt>s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).

Example
Blessed are the <choice>  <sic>cheesemakers</sic>  <corr resp="#editorcert="high">peacemakers</corr> </choice>: for they shall be called the children of God.
Example
<!-- in the <text> ... --><lg> <!-- ... -->  <l>Punkes, Panders, baſe extortionizing    sla<choice>    <sic>n</sic>    <corr resp="#JENS1_transcriber">u</corr>   </choice>es,</l> <!-- ... --> </lg> <!-- in the <teiHeader> ... --> <!-- ... --> <respStmt xml:id="JENS1_transcriber">  <resp when="2014">Transcriber</resp>  <name>Janelle Jenstad</name> </respStmt>

3.30. att.global.source

att.global.source provides attributes used by elements to point to an external source. [1.3.1.1.4. Sources, certainty, and responsibility 3.3.3. Quotation 8.3.4. Writing]
Moduletei
Membersatt.global[TEI abbr abstract add addName addrLine address affiliation age altIdent alternate analytic anyElement appInfo application argument att attDef attList attRef author authority availability back bibl biblFull biblScope biblStruct binaryObject birth bloc body byline cRefPattern calendar calendarDesc catDesc catRef category cb change choice cit citeData citeStructure citedRange classCode classDecl classRef classSpec classes climate closer code constraint constraintSpec content conversion corr correction correspAction correspContext correspDesc country creation dataFacet dataRef dataSpec datatype date dateline death defaultVal del desc distinct distributor district div div1 div2 div3 div4 div5 div6 div7 divGen docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl education eg egXML elementRef elementSpec ellipsis email emph empty encodingDesc epigraph equiv event eventName exemplum expan extent faith fileDesc floatingText floruit foreign forename front funder gap gb genName gender geo geoDecl geogFeat geogName gi gloss graphic group handNote head headItem headLabel hi hyphenation ident idno imprimatur imprint index interpretation item keywords l label langKnowledge langKnown langUsage language lb lg licence list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listPrefixDef listRef listRelation location macroRef macroSpec measure measureGrp media meeting memberOf mentioned milestone model modelGrp modelSequence moduleRef moduleSpec monogr name nameLink namespace nationality normalization note noteGrp notesStmt num nym object objectIdentifier objectName occupation offset opener org orgName orig outputRendition p param paramList paramSpec pb persName persPronouns person personGrp persona place placeName population postBox postCode postscript prefixDef principal profileDesc projectDesc ptr pubPlace publicationStmt publisher punctuation q quotation quote rb ref refState refsDecl reg region relatedItem relation remarks rendition residence resp respStmt revisionDesc roleName rs rt ruby said salute samplingDecl schemaRef schemaSpec scriptNote segmentation sequence series seriesStmt settlement sex sic signed soCalled socecStatus sourceDesc sp speaker specDesc specGrp specGrpRef specList sponsor stage state stdVals street styleDefDecl surname tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term terrain text textClass textLang textNode time title titlePage titlePart titleStmt trailer trait unclear unit unitDecl unitDef val valDesc valItem valList xenoData]
Attributes
sourcespecifies the source from which some aspect of this element is drawn.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Schematron
<sch:rule context="tei:*[@source]"> <sch:let name="srcs"  value="tokenize( normalize-space(@source),' ')"/> <sch:report test="( self::tei:classRef | self::tei:dataRef | self::tei:elementRef | self::tei:macroRef | self::tei:moduleRef | self::tei:schemaSpec ) and $srcs[2]"> When used on a schema description element (like <sch:value-of select="name(.)"/>), the @source attribute should have only 1 value. (This one has <sch:value-of select="count($srcs)"/>.) </sch:report> </sch:rule>
Note

The source attribute points to an external source. When used on an element describing a schema component (<classRef>, <dataRef>, <elementRef>, <macroRef>, <moduleRef>, or <schemaSpec>), it identifies the source from which declarations for the components should be obtained.

On other elements it provides a pointer to the bibliographical source from which a quotation or citation is drawn.

In either case, the location may be provided using any form of URI, for example an absolute URI, a relative URI, a private scheme URI of the form tei:x.y.z, where x.y.z indicates the version number, e.g. tei:4.3.2 for TEI P5 release 4.3.2 or (as a special case) tei:current for whatever is the latest release, or a private scheme URI that is expanded to an absolute URI as documented in a <prefixDef>.

When used on elements describing schema components, source should have only one value; when used on other elements multiple values are permitted.

Example
<p> <!-- ... --> As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>) tells us, <quote source="#mcc_2012">‘Collaboration’ is a problematic and should be a contested    term.</quote> <!-- ... --> </p>
Example
<p> <!-- ... -->  <quote source="#chicago_15_ed">Grammatical theories are in flux, and the more we learn, the    less we seem to know.</quote> <!-- ... --> </p> <!-- ... --> <bibl xml:id="chicago_15_ed">  <title level="m">The Chicago Manual of Style</title>, <edition>15th edition</edition>. <pubPlace>Chicago</pubPlace>: <publisher>University of    Chicago Press</publisher> (<date>2003</date>), <biblScope unit="page">p.147</biblScope>. </bibl>
Example
<elementRef key="psource="tei:2.0.1"/>
Include in the schema an element named <p> available from the TEI P5 2.0.1 release.
Example
<schemaSpec ident="myODD"  source="mycompiledODD.xml"> <!-- further declarations specifying the components required --> </schemaSpec>
Create a schema using components taken from the file mycompiledODD.xml.

3.31. att.handFeatures

att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [12.3.2.1. Document Hands]
Moduletei
MembershandNote scriptNote
Attributes
scribegives a name or other identifier for the scribe believed to be responsible for this hand.
StatusOptional
Datatypeteidata.name
scribeRefpoints to a full description of the scribe concerned, typically supplied by a <person> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
scriptcharacterizes the particular script or writing style used by this hand, for example secretary, copperplate, Chancery, Italian, etc.
StatusOptional
Datatype1–∞ occurrences of teidata.name separated by whitespace
scriptRefpoints to a full description of the script or writing style used by this hand, typically supplied by a <scriptNote> element elsewhere in the description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
mediumdescribes the tint or type of ink, e.g. brown, or other writing medium, e.g. pencil
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
scopespecifies how widely this hand is used in the manuscript.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
sole
only this hand is used throughout the manuscript
major
this hand is used through most of the manuscript
minor
this hand is used occasionally in the manuscript
Note

Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied.

3.32. att.identified

att.identified provides identifying attributes for elements which can be subsequently referenced by means of a key attribute.
Moduletagdocs
MembersattDef classSpec constraintSpec dataSpec elementSpec macroSpec moduleSpec paramSpec schemaSpec
Attributes
identsupplies the identifier by which this element may be referenced.
StatusRequired
Datatypeteidata.name
predeclaresays whether this object should be predeclared in the tei infrastructure module.
StatusOptional
Datatypeteidata.truthValue
Defaultfalse
modulesupplies a name for the module in which this object is to be declared.
StatusOptional
Datatypeteidata.xmlName
Schematron
<sch:rule context="tei:elementSpec[@module]|tei:classSpec[@module]|tei:macroSpec[@module]"> <sch:assert test="(not(ancestor::tei:schemaSpec | ancestor::tei:TEI | ancestor::tei:teiCorpus)) or (not(@module) or (not(//tei:moduleSpec) and not(//tei:moduleRef)) or (//tei:moduleSpec[@ident = current()/@module]) or (//tei:moduleRef[@key = current()/@module]))"> Specification <sch:value-of select="@ident"/>: the value of the module attribute ("<sch:value-of select="@module"/>") should correspond to an existing module, via a moduleSpec or moduleRef</sch:assert> </sch:rule>

3.33. att.internetMedia

att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy.
Moduletei
Membersatt.media[binaryObject graphic media] equiv ptr ref
Attributes
mimeType(MIME media type) specifies the applicable multimedia internet mail extension (MIME) media type
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
ExampleIn this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8.
<ref mimeType="application/tei+xml; charset=UTF-8"  target="https://raw.githubusercontent.com/TEIC/TEI/dev/P5/Source/guidelines-en.xml"/>
Note

This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list.

3.34. att.locatable

att.locatable provides attributes for referencing locations by pointing to entries in a canonical list of places. [2.3.9. The Unit Declaration 14.3.4.3. States, Traits, and Events]
Moduletei
Membersconversion event
Attributes
whereindicates one or more locations by pointing to a <place> element or other canonical description.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace

3.35. att.measurement

att.measurement provides attributes to represent a regularized or normalized measurement.
Moduletei
Membersmeasure measureGrp unit
Attributes
unit(unit) indicates the units used for the measurement, usually using the standard symbol for the desired units.
StatusOptional
Datatypeteidata.enumerated
Suggested values include:
m
(metre) SI base unit of length
kg
(kilogram) SI base unit of mass
s
(second) SI base unit of time
Hz
(hertz) SI unit of frequency
Pa
(pascal) SI unit of pressure or stress
Ω
(ohm) SI unit of electric resistance
L
(litre) 1 dm³
t
(tonne) 10³ kg
ha
(hectare) 1 hm²
Å
(ångström) 10⁻¹⁰ m
mL
(millilitre)
cm
(centimetre)
dB
(decibel) see remarks, below
kbit
(kilobit) 10³ or 1000 bits
Kibit
(kibibit) 2¹⁰ or 1024 bits
kB
(kilobyte) 10³ or 1000 bytes
KiB
(kibibyte) 2¹⁰ or 1024 bytes
MB
(megabyte) 10⁶ or 1 000 000 bytes
MiB
(mebibyte) 2²⁰ or 1 048 576 bytes
Note

If the measurement being represented is not expressed in a particular unit, but rather is a number of discrete items, the unit count should be used, or the unit attribute may be left unspecified.

Wherever appropriate, a recognized SI unit name should be used (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). The list above is indicative rather than exhaustive.

unitRefpoints to a unique identifier stored in the xml:id of a <unitDef> element that defines a unit of measure.
StatusOptional
Datatypeteidata.pointer
quantity(quantity) specifies the number of the specified units that comprise the measurement
StatusOptional
Datatypeteidata.numeric
commodity(commodity) indicates the substance that is being measured
StatusOptional
Datatype1–∞ occurrences of teidata.word separated by whitespace
Note

In general, when the commodity is made of discrete entities, the plural form should be used, even when the measurement is of only one of them.

Schematron
<sch:rule context="tei:*[@unitRef]"> <sch:report test="@unit" role="info">The @unit attribute may be unnecessary when @unitRef is present.</sch:report> </sch:rule>
Note
This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system.
<l>So weren't you gonna buy <measure quantity="0.5unit="gal"   commodity="ice cream">half    a gallon</measure>, baby</l> <l>So won't you go and buy <measure quantity="1.893unit="L"   commodity="ice cream">half    a gallon</measure>, baby?</l>

The unit should normally be named using the standard symbol for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters.

3.36. att.media

att.media provides attributes for specifying display and related properties of external media.
Moduletei
MembersbinaryObject graphic media
Attributes
widthWhere the media are displayed, indicates the display width
StatusOptional
Datatypeteidata.outputMeasurement
heightWhere the media are displayed, indicates the display height
StatusOptional
Datatypeteidata.outputMeasurement
scaleWhere the media are displayed, indicates a scale factor to be applied when generating the desired display size
StatusOptional
Datatypeteidata.numeric

3.37. att.milestoneUnit

att.milestoneUnit provides attributes to indicate the type of section which is changing at a specific milestone. [3.11.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration]
Modulecore
Membersmilestone refState
Attributes
unitprovides a conventional name for the kind of section changing at this milestone.
StatusRequired
Datatypeteidata.enumerated
Suggested values include:
page
physical page breaks (synonymous with the <pb> element).
column
column breaks.
line
line breaks (synonymous with the <lb> element).
book
any units termed book, liber, etc.
poem
individual poems in a collection.
canto
cantos or other major sections of a poem.
speaker
changes of speaker or narrator.
stanza
stanzas within a poem, book, or canto.
act
acts within a play.
scene
scenes within a play or act.
section
sections of any kind.
absent
passages not present in the reference edition.
unnumbered
passages present in the text, but not to be included as part of the reference.
<milestone n="23"  ed="La"  unit="Dreissiger"/> ... <milestone n="24"  ed="AV"  unit="verse"/> ...
Note

If the milestone marks the beginning of a piece of text not present in the reference edition, the special value absent may be used as the value of unit. The normal interpretation is that the reference edition does not contain the text which follows, until the next <milestone> tag for the edition in question is encountered.

In addition to the values suggested, other terms may be appropriate (e.g. Stephanus for the Stephanus numbers in Plato).

The type attribute may be used to characterize the unit boundary in any respect other than simply identifying the type of unit, for example as word-breaking or not.

3.38. att.namespaceable

att.namespaceable provides attributes indicating the target namespace for an object being created.
Moduletagdocs
MembersattDef elementSpec schemaSpec
Attributes
ns(namespace) specifies the namespace to which the element(s) being specified belongs.
StatusOptional
Datatype0–1 occurrences of teidata.namespace separated by whitespace
Defaulthttp://www.tei-c.org/ns/1.0
Note

When specified on an <elementSpec>, this attribute specifies the namespace of the element being added, deleted, replaced, or changed. When specified on a <schemaSpec>, this attribute specifies the namespace of every element that is added, deleted, replaced, or changed by <elementSpec> children of the <schemaSpec>, or by <elementSpec>s referred to by <specGrpRef> children of the <schemaSpec>, unless overridden by an ns attribute on the <elementSpec>.

Note that the value of ns of <attDef> is not inherited from its ancestors.

3.39. att.naming

att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.6.1. Referring Strings 14.3.7. Names and Nyms]
Moduletei
Membersatt.personal[addName eventName forename genName name objectName orgName persName placeName roleName surname] affiliation author birth bloc climate country death district editor education event geogFeat geogName nationality occupation offset population pubPlace region residence rs settlement socecStatus state terrain trait
Attributes
rolemay be used to specify further information about the entity referenced by this name in the form of a set of whitespace-separated values, for example the occupation of a person, or the status of a place.
StatusOptional
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
nymRef(reference to the canonical name) provides a means of locating the canonical form (nym) of the names associated with the object named by the element bearing it.
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

The value must point directly to one or more XML elements by means of one or more URIs, separated by whitespace. If more than one is supplied, the implication is that the name is associated with several distinct canonical names.

3.40. att.notated

att.notated provides attributes to indicate any specialised notation used for element content.
Moduletei
Membersquote
Attributes
notationnames the notation used for the content of the element.
StatusOptional
Datatypeteidata.enumerated

3.41. att.patternReplacement

att.patternReplacement provides attributes for regular-expression matching and replacement. [17.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method]
Moduleheader
MemberscRefPattern prefixDef
Attributes
matchPatternspecifies a regular expression against which the values of other attributes can be matched.
StatusRequired
Datatypeteidata.pattern
Note

The syntax used should follow that defined by W3C XPath syntax. Note that parenthesized groups are used not only for establishing order of precedence and atoms for quantification, but also for creating subpatterns to be referenced by the replacementPattern attribute.

replacementPatternspecifies a ‘replacement pattern’, that is, the skeleton of a relative or absolute URI containing references to groups in the matchPattern which, once subpattern substitution has been performed, complete the URI.
StatusRequired
Datatypeteidata.replacement
Note

The strings $1, $2 etc. are references to the corresponding group in the regular expression specified by matchPattern (counting open parenthesis, left to right). Processors are expected to replace them with whatever matched the corresponding group in the regular expression.

If a digit preceded by a dollar sign is needed in the actual replacement pattern (as opposed to being used as a back reference), the dollar sign must be written as %24.

3.42. att.personal

att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [14.2.1. Personal Names]
Moduletei
MembersaddName eventName forename genName name objectName orgName persName placeName roleName surname
Attributes
fullindicates whether the name component is given in full, as an abbreviation or simply as an initial.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
yes
(yes) the name component is spelled out in full.[Default]
abb
(abbreviated) the name component is given in an abbreviated form.
init
(initial letter) the name component is indicated only by one initial.
sort(sort) specifies the sort order of the name component in relation to others within the name.
StatusOptional
Datatypeteidata.count

3.43. att.placement

att.placement provides attributes for describing where on the source page or object a textual element appears. [3.5.3. Additions, Deletions, and Omissions 12.3.1.4. Additions and Deletions]
Moduletei
Membersadd head label note noteGrp rt stage trailer
Attributes
placespecifies where this item is placed.
StatusRecommended
Datatype1–∞ occurrences of teidata.enumerated separated by whitespace
Suggested values include:
top
at the top of the page
bottom
at the foot of the page
margin
in the margin (left, right, or both)
opposite
on the opposite, i.e. facing, page
overleaf
on the other side of the leaf
above
above the line
right
to the right, e.g. to the right of a vertical line of text, or to the right of a figure
below
below the line
left
to the left, e.g. to the left of a vertical line of text, or to the left of a figure
end
at the end of e.g. chapter or volume.
inline
within the body of the text.
inspace
in a predefined space, for example left by an earlier scribe.
<add place="margin">[An addition written in the margin]</add> <add place="bottom opposite">[An addition written at the foot of the current page and also on the facing page]</add>
<note place="bottom">Ibid, p.7</note>

3.44. att.pointing

att.pointing provides a set of attributes used by all elements which point to other elements by means of one or more URI references. [1.3.1.1.2. Language Indicators 3.7. Simple Links and Cross-References]
Moduletei
Memberscalendar catRef citedRange gloss licence note noteGrp ptr ref term
Attributes
targetLangspecifies the language of the content to be found at the destination referenced by target, using a ‘language tag’ generated according to BCP 47.
StatusOptional
Datatypeteidata.language
Schematron
<sch:rule context="tei:*[not(self::tei:schemaSpec)][@targetLang]"> <sch:assert test="@target">@targetLang should only be used on <sch:name/> if @target is specified.</sch:assert> </sch:rule>
<linkGrp xml:id="pol-swh_aln_2.1-linkGrp">  <ptr xml:id="pol-swh_aln_2.1.1-ptr"   target="pol/UDHR/text.xml#pol_txt_1-head"   type="tuv"   targetLang="pl"/>  <ptr xml:id="pol-swh_aln_2.1.2-ptr"   target="swh/UDHR/text.xml#swh_txt_1-head"   type="tuv"   targetLang="sw"/> </linkGrp>
In the example above, the <linkGrp> combines pointers at parallel fragments of the Universal Declaration of Human Rights: one of them is in Polish, the other in Swahili.
Note

The value must conform to BCP 47. If the value is a private use code (i.e., starts with x- or contains -x-), a <language> element with a matching value for its ident attribute should be supplied in the TEI header to document this value. Such documentation may also optionally be supplied for non-private-use codes, though these must remain consistent with their (IETF)Internet Engineering Task Force definitions.

targetspecifies the destination of the reference by supplying one or more URI References
StatusOptional
Datatype1–∞ occurrences of teidata.pointer separated by whitespace
Note

One or more syntactically valid URI references, separated by whitespace. Because whitespace is used to separate URIs, no whitespace is permitted inside a single URI. If a whitespace character is required in a URI, it should be escaped with the normal mechanism, e.g. TEI%20Consortium.

evaluate(evaluate) specifies the intended meaning when the target of a pointer is itself a pointer.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
all
if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer.
one
if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer.
none
no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target.
Note

If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers.

3.45. att.predicate

att.predicate provides attributes for filtering by an XPath predicate expression. [23.4. Common Elements 23.5.4.1. The TEI processing model 23.5.4.9. Implementation of Processing Models]
Moduletagdocs
Membersequiv model
Attributes
predicatethe condition under which the element bearing this attribute applies, given as an XPath predicate expression.
StatusOptional
Datatypeteidata.xpath
Note

The XPath predicate expression given as the value of the predicate attribute has to be provided without wrapping square brackets.

Example
<model predicate="parent::person"  behaviour="inline">  <desc versionDate="2015-08-21"   xml:lang="en">If it is a child of a person element, treat as    inline</desc> </model>
ExampleThe following example declares that the <name> element can be mapped to, or is equivalent to, the external concepts of ‘PERSON’ and ‘PLACE’ depending on the ‘XPath’ expression given in predicate
<elementSpec ident="namemode="change">  <equiv name="PERSON"   predicate="@type eq 'person'"   uri="http://www.example.com/entities/person"/>  <equiv name="PLACE"   predicate="@type eq 'place'"   uri="http://www.example.com/entities/place"/> </elementSpec>

3.46. att.ranging

att.ranging provides attributes for describing numerical ranges.
Moduletei
Membersatt.dimensions[add age birth date death del ellipsis floruit gap geogFeat offset population state time trait unclear] measure num
Attributes
atLeastgives a minimum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
atMostgives a maximum estimated value for the approximate measurement.
StatusOptional
Datatypeteidata.numeric
minwhere the measurement summarizes more than one observation or a range, supplies the minimum value observed.
StatusOptional
Datatypeteidata.numeric
maxwhere the measurement summarizes more than one observation or a range, supplies the maximum value observed.
StatusOptional
Datatypeteidata.numeric
confidencespecifies the degree of statistical confidence (between zero and one) that a value falls within the range specified by min and max, or the proportion of observed values that fall within that range.
StatusOptional
Datatypeteidata.probability
Example
The MS. was lost in transmission by mail from <del rend="overstrike">  <gap reason="illegible"   extent="one or two lettersatLeast="1atMost="2unit="chars"/> </del> Philadelphia to the Graphic office, New York.
Example
Americares has been supporting the health sector in Eastern Europe since 1986, and since 1992 has provided <measure atLeast="120000000unit="USD"  commodity="currency">more than $120m</measure> in aid to Ukrainians.

3.47. att.repeatable

att.repeatable provides attributes for the elements which define component parts of a content model.
Moduletagdocs
Membersalternate anyElement classRef datatype elementRef sequence
Attributes
minOccurs(minimum number of occurences) indicates the smallest number of times this component may occur.
StatusOptional
Datatypeteidata.count
Default1
maxOccurs(maximum number of occurences) indicates the largest number of times this component may occur.
StatusOptional
Datatypeteidata.unboundedCount
Default1
Schematron
<sch:rule context="tei:*[ @minOccurs and @maxOccurs ]"> <sch:let name="min"  value="@minOccurs cast as xs:integer"/> <sch:let name="max"  value="if ( normalize-space( @maxOccurs ) eq 'unbounded') then -1 else @maxOccurs cast as xs:integer"/> <sch:assert test="$max eq -1 or $max ge $min">@maxOccurs should be greater than or equal to @minOccurs</sch:assert> </sch:rule> <sch:rule context="tei:*[ @minOccurs and not( @maxOccurs ) ]"> <sch:assert test="@minOccurs cast as xs:integer lt 2">When @maxOccurs is not specified, @minOccurs must be 0 or 1</sch:assert> </sch:rule>
Note

The value of minOccurs must always be less than or equal to that of maxOccurs. Since the default value of maxOccurs is 1, when maxOccurs is not specified minOccurs must always be less than or equal to 1. The default value of minOccurs is also 1, and therefore, when minOccurs is not specified the value of maxOccurs must always be greater than or equal to 1. An ODD processor should raise an error if either of these conditions is not met.

3.48. att.resourced

att.resourced provides attributes by which a resource (such as an externally held media file) may be located.
Moduletei
Membersgraphic media schemaRef
Attributes
url(uniform resource locator) specifies the URL from which the media concerned may be obtained.
StatusRequired
Datatypeteidata.pointer

3.49. att.sortable

att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [10.1. Dictionary Body and Overall Structure]
Moduletei
Membersbibl biblFull biblStruct correspAction event idno item list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRelation nym object org person personGrp persona place relation term
Attributes
sortKeysupplies the sort key for this element in an index, list or group which contains it.
StatusOptional
Datatypeteidata.word
David's other principal backer, Josiah ha-Kohen <index indexName="NAMES">  <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term> </index> b. Azarya, son of one of the last gaons of Sura was David's own first cousin.
Note

The sort key is used to determine the sequence and grouping of entries in an index. It provides a sequence of characters which, when sorted with the other values, will produced the desired order; specifics of sort key construction are application-dependent

Dictionary order often differs from the collation sequence of machine-readable character sets; in English-language dictionaries, an entry for 4-H will often appear alphabetized under ‘fourh’, and McCoy may be alphabetized under ‘maccoy’, while A1, A4, and A5 may all appear in numeric order ‘alphabetized’ between ‘a-’ and ‘AA’. The sort key is required if the orthography of the dictionary entry does not suffice to determine its location.

3.50. att.spanning

att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [12.3.1.4. Additions and Deletions 1.3.1. Attribute Classes]
Moduletei
Memberscb gb index lb milestone pb
Attributes
spanToindicates the end of a span initiated by the element bearing this attribute.
StatusOptional
Datatypeteidata.pointer
SchematronThe @spanTo attribute must point to an element following the current element
<sch:rule context="tei:*[@spanTo]"> <sch:assert test="id(substring(@spanTo,2)) and following::*[@xml:id=substring(current()/@spanTo,2)]">The element indicated by @spanTo (<sch:value-of select="@spanTo"/>) must follow the current element <sch:name/> </sch:assert> </sch:rule>
Note

The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself.

3.51. att.styleDef

att.styleDef provides attributes to specify the name of a formal definition language used to provide formatting or rendition information.
Moduletei
Membersrendition styleDefDecl
Attributes
schemeidentifies the language used to describe the rendition.
StatusOptional
Datatypeteidata.enumerated
Legal values are:
css
Cascading Stylesheet Language
xslfo
Extensible Stylesheet Language Formatting Objects
free
Informal free text description
other
A user-defined rendition description language
Note

If no value for the @scheme attribute is provided, then the default assumption should be that CSS is in use.

schemeVersionsupplies a version number for the style language provided in scheme.
StatusOptional
Datatypeteidata.versionNumber
Schematron
<sch:rule context="tei:*[@schemeVersion]"> <sch:assert test="@scheme and not(@scheme = 'free')"> @schemeVersion can only be used if @scheme is specified. </sch:assert> </sch:rule>
Note

If schemeVersion is used, then scheme should also appear, with a value other than free.

3.52. att.timed

att.timed provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map. [8.3.5. Temporal Information]
Moduletei
MembersbinaryObject ellipsis gap media
Attributes
startindicates the location within a temporal alignment at which this element begins.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to follow the immediately preceding element at the same hierarchic level.

endindicates the location within a temporal alignment at which this element ends.
StatusOptional
Datatypeteidata.pointer
Note

If no value is supplied, the element is assumed to precede the immediately following element at the same hierarchic level.

3.53. att.transcriptional

att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [12.3.1.4. Additions and Deletions]
Moduletei
Membersadd del rt
Attributes
statusindicates the effect of the intervention, for example in the case of a deletion, strikeouts which include too much or too little text, or in the case of an addition, an insertion which duplicates some of the text already present.
StatusOptional
Datatypeteidata.enumerated
Sample values include:
duplicate
all of the text indicated as an addition duplicates some text that is in the original, whether the duplication is word-for-word or less exact.
duplicate-partial
part of the text indicated as an addition duplicates some text that is in the original
excessStart
some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excessEnd
some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
shortStart
some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
shortEnd
some text at the end of the deletion is not marked as deleted even though it clearly should be.
partial
some text in the deletion is not marked as deleted even though it clearly should be.
unremarkable
the deletion is not faulty.[Default]
Note

Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts; status information on additions is even less common.

Marking a deletion or addition as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

causedocuments the presumed cause for the intervention.
StatusOptional
Datatypeteidata.enumerated
seq(sequence) assigns a sequence number related to the order in which the encoded features carrying this attribute are believed to have occurred.
StatusOptional
Datatypeteidata.count

3.54. att.translatable

att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document.
Moduletagdocs
Membersdesc exemplum gloss remarks valDesc
Attributes
versionDatespecifies the date on which the source text was extracted and sent to the translator
StatusOptional
Datatypeteidata.temporal.working
Note

The versionDate attribute can be used to determine whether a translation might need to be revisited, by comparing the modification date on the containing file with the versionDate value on the translation. If the file has changed, changelogs can be checked to see whether the source text has been modified since the translation was made.

3.55. att.typed

att.typed provides attributes that can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 18.1.1. Words and Above 3.6.1. Referring Strings 3.7. Simple Links and Cross-References 3.6.5. Abbreviations and Their Expansions 3.13.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 14.3.2.3. Personal Relationships 12.3.1.1. Core Elements for Transcriptional Work 17.1.1. Pointers and Links 17.3. Blocks, Segments, and Anchors 13.2. Linking the Apparatus to the Text 23.5.1.2. Defining Content Models: RELAX NG 8.3. Elements Unique to Spoken Texts 24.3.1.3. Modification of Attribute and Attribute Value Lists]
Moduletei
MembersTEI abbr add addName affiliation age altIdent application bibl biblStruct binaryObject birth bloc calendar cb change cit classSpec climate constraintSpec corr correspAction correspDesc country date death del desc distinct district div div1 div2 div3 div4 div5 div6 div7 divGen education event eventName exemplum faith floatingText forename gb genName gender geogFeat geogName gloss graphic group head ident idno label langKnowledge lb lg list listBibl listChange listEvent listNym listObject listOrg listPerson listPlace listRef listRelation location measure measureGrp media milestone moduleSpec name nameLink nationality note noteGrp num nym object objectName occupation offset org orgName pb persName persPronouns place placeName population ptr quote rb ref reg region relatedItem relation residence roleName rs rt ruby schemaRef settlement sex socecStatus state surname tag teiCorpus term terrain text time title titlePage titlePart trailer trait unit unitDef xenoData
Attributes
typecharacterizes the element in some sense, using any convenient classification scheme or typology.
StatusOptional
Datatypeteidata.enumerated
<div type="verse">  <head>Night in Tarras</head>  <lg type="stanza">   <l>At evening tramping on the hot white road</l>   <l></l>  </lg>  <lg type="stanza">   <l>A wind sprang up from nowhere as the sky</l>   <l></l>  </lg> </div>
Note

The type attribute is present on a number of elements, not all of which are members of att.typed, usually because these elements restrict the possible values for the attribute in a specific way.

subtype(subtype) provides a sub-categorization of the element, if needed
StatusOptional
Datatypeteidata.enumerated
Note

The subtype attribute may be used to provide any sub-classification for the element additional to that provided by its type attribute.

Schematron
<sch:rule context="tei:*[@subtype]"> <sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype unless also categorized in general with @type</sch:assert> </sch:rule>
Note

When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 24.3.1.3. Modification of Attribute and Attribute Value Lists .

3.56. att.written

att.written provides attributes to indicate the hand in which the content of an element was written in the source being transcribed. [1.3.1. Attribute Classes]
Moduletei
Membersatt.transcriptional[add del rt] closer div head hi label note noteGrp opener p postscript salute signed stage text trailer
Attributes
handpoints to a <handNote> element describing the hand considered responsible for the content of the element concerned.
StatusOptional
Datatypeteidata.pointer

4. Macros

4.1. macro.limitedContent

macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.inter"/>
 </alternate>
</content>
    
Declaration
tei_macro.limitedContent =
   ( text | tei_model.limitedPhrase | tei_model.inter )*

4.2. macro.paraContent

macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.paraPart"/>
 </alternate>
</content>
    
Declaration
tei_macro.paraContent = ( text | tei_model.paraPart )*

4.3. macro.phraseSeq

macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.attributable"/>
  <classRef key="model.phrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq =
   (
      text
    | tei_model.gLike
    | tei_model.attributable
    | tei_model.phrase
    | tei_model.global
   )*

4.4. macro.phraseSeq.limited

macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.limitedPhrase"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.phraseSeq.limited =
   ( text | tei_model.limitedPhrase | tei_model.global )*

4.5. macro.specialPara

macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System]
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.divPart"/>
  <classRef key="model.global"/>
 </alternate>
</content>
    
Declaration
tei_macro.specialPara =
   (
      text
    | tei_model.gLike
    | tei_model.phrase
    | tei_model.inter
    | tei_model.divPart
    | tei_model.global
   )*

4.6. macro.xtext

macro.xtext (extended text) defines a sequence of character data and gaiji elements.
Moduletei
Used by
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <classRef key="model.gLike"/>
 </alternate>
</content>
    
Declaration
tei_macro.xtext = ( text | tei_model.gLike )*

5. Datatypes

5.1. teidata.certainty

teidata.certainty defines the range of attribute values expressing a degree of certainty.
Moduletei
Used by
Content model
<content>
 <valList type="closed">
  <valItem ident="high"/>
  <valItem ident="medium"/>
  <valItem ident="low"/>
  <valItem ident="unknown"/>
 </valList>
</content>
    
Declaration
tei_teidata.certainty = "high" | "medium" | "low" | "unknown"
Note

Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter.

5.2. teidata.count

teidata.count defines the range of attribute values used for a non-negative integer value used as a count.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="nonNegativeInteger"/>
</content>
    
Declaration
tei_teidata.count = xsd:nonNegativeInteger
Note

Any positive integer value or zero is permitted

5.3. teidata.duration.iso

teidata.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
</content>
    
Declaration
tei_teidata.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Example
<time dur-iso="PT0,75H">three-quarters of an hour</time>
Example
<date dur-iso="P1,5D">a day and a half</date>
Example
<date dur-iso="P14D">a fortnight</date>
Example
<time dur-iso="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times.

5.4. teidata.duration.w3c

teidata.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes.
Moduletei
Used by
Content model
<content>
 <dataRef name="duration"/>
</content>
    
Declaration
tei_teidata.duration.w3c = xsd:duration
Example
<time dur="PT45M">forty-five minutes</time>
Example
<date dur="P1DT12H">a day and a half</date>
Example
<date dur="P7D">a week</date>
Example
<time dur="PT0.02S">20 ms</time>
Note

A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.

For complete details, see the W3C specification.

5.5. teidata.enumerated

teidata.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities.
Moduletei
Used by
teidata.gender teidata.sexElement:
Content model
<content>
 <dataRef key="teidata.word"/>
</content>
    
Declaration
tei_teidata.enumerated = teidata.word
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element.

5.6. teidata.gender

teidata.gender defines the range of attribute values used to represent the gender of a person, persona, or character.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
tei_teidata.gender = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

Values for this datatype should not be used to encode morphological gender (cf. <gen>, msd as defined in att.linguistic, and 10.3.1. Information on Written and Spoken Forms).

5.7. teidata.language

teidata.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification]
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="language"/>
  <valList>
   <valItem ident=""/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.language = xsd:language | ( "" )
Note

The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.

A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.

language
The IANA-registered code for the language. This is almost always the same as the ISO 639 2-letter language code if there is one. The list of available registered language subtags can be found at https://www.iana.org/assignments/language-subtag-registry. It is recommended that this code be written in lower case.
script
The ISO 15924 code for the script. These codes consist of 4 letters, and it is recommended they be written with an initial capital, the other three letters in lower case. The canonical list of codes is maintained by the Unicode Consortium, and is available at https://unicode.org/iso15924/iso15924-codes.html. The IETF recommends this code be omitted unless it is necessary to make a distinction you need.
region
Either an ISO 3166 country code or a UN M.49 region code that is registered with IANA (not all such codes are registered, e.g. UN codes for economic groupings or codes for countries for which there is already an ISO 3166 2-letter code are not registered). The former consist of 2 letters, and it is recommended they be written in upper case; the list of codes can be searched or browsed at https://www.iso.org/obp/ui/#search/code/. The latter consist of 3 digits; the list of codes can be found at http://unstats.un.org/unsd/methods/m49/m49.htm.
variant
An IANA-registered variation. These codes ‘are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags’.
extension
An extension has the format of a single letter followed by a hyphen followed by additional subtags. These exist to allow for future extension to BCP 47, but as of this writing no such extensions are in use.
private use
An extension that uses the initial subtag of the single letter x (i.e., starts with x-) has no meaning except as negotiated among the parties involved. These should be used with great care, since they interfere with the interoperability that use of RFC 4646 is intended to promote. In order for a document that makes use of these subtags to be TEI-conformant, a corresponding <language> element must be present in the TEI header.

There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications.

Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.

Examples include

sn
Shona
zh-TW
Taiwanese
zh-Hant-HK
Chinese written in traditional script as used in Hong Kong
en-SL
English as spoken in Sierra Leone
pl
Polish
es-MX
Spanish as spoken in Mexico
es-419
Spanish as spoken in Latin America

The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML.

5.8. teidata.name

teidata.name defines the range of attribute values expressed as an XML Name.
Moduletei
Used by
att giElement:
Content model
<content>
 <dataRef name="Name"/>
</content>
    
Declaration
tei_teidata.name = xsd:Name
Note

Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see https://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits.

5.9. teidata.namespace

teidata.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
tei_teidata.namespace = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax

5.10. teidata.namespaceOrName

teidata.namespaceOrName defines attribute values which contain either an absolute namespace URI or a qualified XML name.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="anyURI">
   <dataFacet name="pattern"
    value="[^/\s]+:\S*"/>
  </dataRef>
  <dataRef name="Name">
   <dataFacet name="pattern" value=".+:.+"/>
  </dataRef>
 </alternate>
</content>
    
Declaration
tei_teidata.namespaceOrName = xsd:anyURI | xsd:Name

5.11. teidata.numeric

teidata.numeric defines the range of attribute values used for numeric values.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="double"/>
  <dataRef name="token"
   restriction="(\-?[\d]+/\-?[\d]+)"/>
  <dataRef name="decimal"/>
 </alternate>
</content>
    
Declaration
tei_teidata.numeric =
   xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal
Note

Any numeric value, represented as a decimal number, in floating point format, or as a ratio.

To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3.

A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2.

5.12. teidata.outputMeasurement

teidata.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display.
Moduletei
Used by
Content model
<content>
 <dataRef name="token"
  restriction="[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"/>
</content>
    
Declaration
tei_teidata.outputMeasurement =
   token
   {
      pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|ch|rem|vw|vh|vmin|vmax)"
   }
Example
<figure>  <head>The TEI Logo</head>  <figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in    between and <mentioned>text encoding initiative</mentioned> underneath, all on a white    background.</figDesc>  <graphic height="600pxwidth="600px"   url="http://www.tei-c.org/logos/TEI-600.jpg"/> </figure>
Note

These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft.

5.13. teidata.pattern

teidata.pattern defines attribute values which are expressed as a regular expression.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"/>
</content>
    
Declaration
tei_teidata.pattern = token
Note
A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern H(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings)
Wikipedia

This TEI datatype is mapped to the XSD token datatype, and may therefore contain any string of characters. However, it is recommended that the value used conform to the particular flavour of regular expression syntax supported by XSD Schema.

5.14. teidata.pointer

teidata.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef restriction="\S+" name="anyURI"/>
</content>
    
Declaration
tei_teidata.pointer = xsd:anyURI { pattern = "\S+" }
Note

The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/

5.15. teidata.prefix

teidata.prefix defines a range of values that may function as a URI scheme name.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[a-z][a-z0-9\+\.\-]*"/>
</content>
    
Declaration
tei_teidata.prefix = token { pattern = "[a-z][a-z0-9\+\.\-]*" }
Note

This datatype is used to constrain a string of characters to one that can be used as a URI scheme name according to RFC 3986, section 3.1. Thus only the 26 lowercase letters a–z, the 10 digits 0–9, the plus sign, the period, and the hyphen are permitted, and the value must start with a letter.

5.16. teidata.probCert

teidata.probCert defines a range of attribute values which can be expressed either as a numeric probability or as a coded certainty value.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef key="teidata.probability"/>
  <dataRef key="teidata.certainty"/>
 </alternate>
</content>
    
Declaration
tei_teidata.probCert = teidata.probability | teidata.certainty

5.17. teidata.probability

teidata.probability defines the range of attribute values expressing a probability.
Moduletei
Used by
Content model
<content>
 <dataRef name="double">
  <dataFacet name="minInclusive" value="0"/>
  <dataFacet name="maxInclusive" value="1"/>
 </dataRef>
</content>
    
Declaration
tei_teidata.probability = xsd:double
Note

Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true.

5.18. teidata.replacement

teidata.replacement defines attribute values which contain a replacement template.
Moduletei
Used by
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.replacement = text

5.19. teidata.sex

teidata.sex defines the range of attribute values used to identify the sex of an organism.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef key="teidata.enumerated"/>
</content>
    
Declaration
tei_teidata.sex = teidata.enumerated
Note

Values for attributes using this datatype may be defined locally by a project, or they may refer to an external standard.

5.20. teidata.temporal.iso

teidata.temporal.iso defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the international standard Data elements and interchange formats – Information interchange – Representation of dates and times.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
  <dataRef name="token"
   restriction="[0-9.,DHMPRSTWYZ/:+\-]+"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.iso =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
 | token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

For all representations for which ISO 8601:2004 describes both a basic and an extended format, these Guidelines recommend use of the extended format.

5.21. teidata.temporal.w3c

teidata.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"/>
  <dataRef name="gYear"/>
  <dataRef name="gMonth"/>
  <dataRef name="gDay"/>
  <dataRef name="gYearMonth"/>
  <dataRef name="gMonthDay"/>
  <dataRef name="time"/>
  <dataRef name="dateTime"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.w3c =
   xsd:date
 | xsd:gYear
 | xsd:gMonth
 | xsd:gDay
 | xsd:gYearMonth
 | xsd:gMonthDay
 | xsd:time
 | xsd:dateTime
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

5.22. teidata.temporal.working

teidata.temporal.working defines the range of values, conforming to the W3C XML Schema Part 2: Datatypes Second Edition specification, expressing a date or a date and a time within the working life of the document.
Moduletei
Used by
Content model
<content>
 <alternate>
  <dataRef name="date"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
  <dataRef name="dateTime"
   restriction="(19[789][0-9]|[2-9][0-9]{3}).*"/>
 </alternate>
</content>
    
Declaration
tei_teidata.temporal.working =
   xsd:date { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
 | xsd:dateTime { pattern = "(19[789][0-9]|[2-9][0-9]{3}).*" }
Note

If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used.

The earliest time expressable with this datatype is 01 January 1970 (the Unix Epoch), which could be written as either 1970-01-01 or 1970-01-01T00:00:00Z.

5.23. teidata.text

teidata.text defines the range of attribute values used to express some kind of identifying string as a single sequence of Unicode characters possibly including whitespace.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="string"/>
</content>
    
Declaration
tei_teidata.text = string
Note

Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted.

5.24. teidata.truthValue

teidata.truthValue defines the range of attribute values used to express a truth value.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="boolean"/>
</content>
    
Declaration
tei_teidata.truthValue = xsd:boolean
Note

The possible values of this datatype are 1 or true, or 0 or false.

This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: teidata.xTruthValue.

5.25. teidata.unboundedCount

teidata.unboundedCount defines the range of values used for a counting number or the string unbounded for infinity.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="nonNegativeInteger"/>
  <valList type="closed">
   <valItem ident="unbounded"/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.unboundedCount = xsd:nonNegativeInteger | ( "unbounded" )

5.26. teidata.version

teidata.version defines the range of attribute values which may be used to specify a TEI or Unicode version number.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+(\.[\d]+){0,2}"/>
</content>
    
Declaration
tei_teidata.version = token { pattern = "[\d]+(\.[\d]+){0,2}" }
Note

The value of this attribute follows the pattern specified by the Unicode consortium for its version number (https://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied.

5.27. teidata.versionNumber

teidata.versionNumber defines the range of attribute values used for version numbers.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="token"
  restriction="[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}"/>
</content>
    
Declaration
tei_teidata.versionNumber =
   token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" }

5.28. teidata.word

teidata.word defines the range of attribute values expressed as a single word or token.
Moduletei
Used by
teidata.enumeratedElement:
Content model
<content>
 <dataRef name="token"
  restriction="[^\p{C}\p{Z}]+"/>
</content>
    
Declaration
tei_teidata.word = token { pattern = "[^\p{C}\p{Z}]+" }
Note

Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace.

5.29. teidata.xTruthValue

teidata.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown.
Moduletei
Used by
Element:
Content model
<content>
 <alternate>
  <dataRef name="boolean"/>
  <valList>
   <valItem ident="unknown"/>
   <valItem ident="inapplicable"/>
  </valList>
 </alternate>
</content>
    
Declaration
tei_teidata.xTruthValue = xsd:boolean | ( "unknown" | "inapplicable" )
Note

In cases where where uncertainty is inappropriate, use the datatype teidata.TruthValue.

5.30. teidata.xmlName

teidata.xmlName defines attribute values which contain an XML name.
Moduletei
Used by
Element:
Content model
<content>
 <dataRef name="NCName"/>
</content>
    
Declaration
tei_teidata.xmlName = xsd:NCName
Note

The rules defining an XML name form a part of the XML Specification.

5.31. teidata.xpath

teidata.xpath defines attribute values which contain an XPath expression.
Moduletei
Used by
Element:
Content model
<content>
 <textNode/>
</content>
    
Declaration
tei_teidata.xpath = text
Note

Any XPath expression using the syntax defined in 6.2..

When writing programs that evaluate XPath expressions, programmers should be mindful of the possibility of malicious code injection attacks. For further information about XPath injection attacks, see the article at OWASP.

Ashton, Knox and Aya. Date: 2025-10-23